Skip to main content
Glama
Sign In
atlaspi-mcp

atlaspi-mcp

by Soil911
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_route

Retrieve detailed information about a historical commercial route, including waypoints, commodities, and ethical notes, with specific documentation of Atlantic slave trade routes.

Instructions

Dettaglio di una rotta commerciale: nome originale, tipo geografico, intervallo temporale, waypoints (città attraversate in ordine) con coordinate, commodities principali, flag involves_slavery, geometry_geojson per visualizzazione, ethical_notes dettagliate. ETHICS-010: le rotte della tratta atlantica documentano le stime di Middle Passage (~1.8M morti su 12.5M embarcati).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "route_id": "<route_id>"
    },
    "name": "get_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
route_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.3

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It implies read-only behavior ('dettaglio') and discloses sensitive content (ethical notes about slave trade). However, it does not explicitly state that the tool is non-destructive or require authentication, leaving some gaps for a new user.

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 a compact single sentence listing key output fields. It is front-loaded with the core purpose. The inclusion of a specific ethical note adds value without excessive length, though it could be streamlined.

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

Completeness3/5

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

Given there is no output schema, the description serves as the sole documentation of return fields. It covers most vital elements, but omits input explanation and does not describe pagination or response format. For a simple get-by-ID tool, it is adequate but has gaps.

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

Parameters1/5

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

The input schema has one required parameter (route_id) with no description. The tool description adds no information about this parameter; it only describes the output. With 0% schema coverage and no parameter explanation, this dimension is severely lacking.

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

Purpose4/5

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

The description clearly states the tool returns details of a commercial route, listing specific fields like waypoints with coordinates, commodities, and ethical notes. It distinguishes from siblings like search_routes or get_chain by focusing on a single route's full detail, but it does not explicitly mention the input parameter, which slightly reduces clarity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as search_routes (for finding routes) or get_chain (for chain details). The description does not include when/why to use it, leaving the agent to infer from the name and siblings.

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

Deploy Server

Other Tools