← All engines

RUST ENGINE / tour_profile

Planar tour instance profile

Inspect distances, isolation and shape in a planar point cloud (3–256 points), with explicit handling of coincident points and undetermined principal axes.

Emerald and gold point clusters on a glass geometry table with measuring axes and a distance histogram.
Concept illustration — not calculation evidence. Run the demonstration to inspect the returned data.
Open the tour_profile demonstration ↗Try the live calculation ↗Connect an AI assistant →

What does a real call return?

For a unit square with its centre point, the largest pairwise distance is 1.414 and the mean pairwise distance 0.966. Principal axes are reported as undefined, because the covariance is isotropic.

Recorded on 2 November 2026 through the public MCP endpoint, service release 0.17.1. Inputs and full responses, response SHA-256 4b9ab5b79e6d…. Verdict values are the literal values the tool returns. Run the same inputs yourself to compare; elapsed times vary, and a new release may change the figures.

Checked against

Recorded on release 0.16.1. These checks cover the listed cases, not every input. Evidence cards.

How it works

Pairwise distance statistics, k-nearest isolation in the Method Lab convention, centroid centrality, PCA collinearity, mirror residual across the better principal axis when those axes are determined, an eight-bin distance histogram and a rounded fingerprint. Deterministic and geometry-only.

Inputs and units

Provide 3 to 256 planar points with finite coordinates in consistent units, and optionally a reference distance fraction between 0.01 and 0.5 for the close-pair test.

What the result contains

The full descriptor set, the histogram and a rounded fingerprint, with explicit limits. The principal-axis mirror residual is null for isotropic noncoincident covariance. It recommends no method, promotes nothing and validates no benefit.

Example MCP call

{
  "name": "tour_profile",
  "arguments": {
    "points": [
      {
        "x": 0,
        "y": 0
      },
      {
        "x": 1,
        "y": 0
      },
      {
        "x": 1,
        "y": 1
      },
      {
        "x": 0,
        "y": 1
      },
      {
        "x": 0.5,
        "y": 0.5
      }
    ]
  }
}

Send this tool name and arguments through a connected MCP client. Discover the authoritative input schema with tools/list.

Call this engine in one command

Node.js 20+ and npm. This downloads a small remote MCP client; it does not install the engine locally.

npx --yes --package https://scorecompute.com/downloads/scorecompute-call-0.14.2.tgz scorecompute-call tour_profile --arguments '{"points":[{"x":0,"y":0},{"x":1,"y":0},{"x":1,"y":1},{"x":0,"y":1},{"x":0.5,"y":0.5}]}'

Client download, PowerShell input and verification →

Direct MCP access

tour_profile is independently callable. It is deliberately not connected to the automatic planner, so nothing passes its results to another engine for you. Two tools returning similar JSON fields does not mean their results are compatible.

Cite this engine

Version 0.2.0, source SHA-256 51b1943a8409…. Evidence recorded on release 0.16.1; the public service currently runs 0.17.1. Replace the access date when you cite it.

ScoreCompute. Planar tour instance profile (tour_profile), version 0.2.0, source SHA-256 51b1943a84091457dc87d71e4cd2895bd6b92271fc7fc807e66bf48ebadb213e. Evidence release 0.16.1, service release 0.17.1. https://scorecompute.com/engines/tour-profile/ (accessed YYYY-MM-DD).

All engine citations · Evidence card

Execution and availability

ScoreCompute exposes this tool through MCP Streamable HTTP. Rust computation runs on a connected worker; the public website and MCP gateway run separately. Among these 22 scientific tools, CUDA is implemented for simulate_pi; the other scientific engines run on CPU. The separate contributor network runs two compiled public workloads: a π estimate and fixed synthetic schedule probes. Requests are bounded and concurrent work may be refused when capacity is occupied.

Record inputs, assumptions and returned provenance when sharing a result. The public observatory displays software client names and tool activity, without publishing calculation arguments or results.

Explore another engine →Agent-readable overview ↗

Sources

These publications describe the method or a reference used in its tests. Citing them does not certify this implementation.

First published 5 October 2026 · Last updated 2 November 2026