Skip to main content
Glama

TrustyData

by app.trustydata
OverviewDiscussionsAdmin

Matrice de temps et de distances

route_matrix
Read-onlyIdempotent

Calcule une matrice de distances et durées entre N origines et M destinations (jusqu'à 25×25) sur le réseau France (OpenStreetMap), au choix en voiture, à pied ou à vélo. Sans géométrie ni consignes : pour un itinéraire détaillé, utilise compute_route. Mode de déplacement : car (voiture, défaut), walking (à pied) ou cycling (à vélo). Les valeurs du contrat d'API (auto, pieton, velo) sont acceptées telles quelles. ⚠️ La matrice plafonne à 1 500 km en voiture et à 200 km à pied comme à vélo — des limites plus basses que compute_route (5 000 / 250 / 500 km) : un trajet que compute_route accepte peut être refusé ici, en 422. Plan minimum : Growth. Mention OSM ODbL obligatoire.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoMode de déplacement : `car` (défaut), `walking` ou `cycling`.
originsYesPoints de départ (1 à 25), chacun une adresse libre OU un couple `lat`/`lon`.
destinationsYesPoints d'arrivée (1 à 25), même forme.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / destinations / description
      Added value: +"Points d'arrivée (1 à 25), même forme."
    • addedInput schema / properties / destinations / items / properties / lat / description
      Added value: +"Latitude WGS84, avec `lon` (XOR address)."
    • addedInput schema / properties / destinations / items / properties / lon / description
      Added value: +"Longitude WGS84, avec `lat` (XOR address)."
    • addedInput schema / properties / mode / description
      Added value: +"Mode de déplacement : `car` (défaut), `walking` ou `cycling`."
    • addedInput schema / properties / origins / description
      Added value: +"Points de départ (1 à 25), chacun une adresse libre OU un couple `lat`/`lon`."
    • addedInput schema / properties / origins / items / properties / lat / description
      Added value: +"Latitude WGS84, avec `lon` (XOR address)."
    • addedInput schema / properties / origins / items / properties / lon / description
      Added value: +"Longitude WGS84, avec `lat` (XOR address)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / destinations / items / description
      Added value: +"A ``RoutePoint`` is EITHER a free-text ``address`` OR a ``lat``/``lon`` couple\n(mutually exclusive), mirroring trusty-service's ``RouteEndpointInput``."
    • addedInput schema / properties / origins / items / description
      Added value: +"A ``RoutePoint`` is EITHER a free-text ``address`` OR a ``lat``/``lon`` couple\n(mutually exclusive), mirroring trusty-service's ``RouteEndpointInput``."
  3. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds substantial operational context: network (France OSM), matrix cap (25×25), per-mode distance ceilings, the 422 error case, plan requirement (Growth), and mandatory OSM ODbL attribution. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place: purpose, alternative, modes, limits, and attribution. It front-loads the core function and scopes before constraints. Slightly long but well-organized in a way that supports quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return details are handled elsewhere. The description covers everything an agent needs to call correctly: what it does, network, modes, legacy values, limits, error behavior, plan, and attribution. Nothing essential is missing for safe and correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by documenting legacy mode values (`auto`, `pieton`, `velo`) accepted as-is, which the schema does not mention. It also reinforces the XOR lat/lon vs address semantics already present in the schema. This extra semantic detail justifies moving above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Calcule une matrice de distances et durées entre N origines et M destinations' and immediately scopes it to France/OSM with mode options. It also explicitly contrasts with the sibling compute_route ('Sans géométrie ni consignes'), making the distinction unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly tells the agent when to use this tool vs its sibling: 'pour un itinéraire détaillé, utilise compute_route'. It also warns that matrix distance limits (1500 km car, 200 km walk/bike) are lower than compute_route, so a route accepted there may be rejected here with a 422. This gives explicit when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TrustyData toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources