Skip to main content
Glama
Sign In
Piloterr MCP Server

Piloterr MCP Server

Official
by piloterr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Describe a Piloterr endpoint

get_endpoint
Read-only

Retrieve an endpoint's description and parameter details—names, types, required fields, and allowed values—by its name from search results so you can inspect it before calling.

Instructions

Returns the description and parameters (names, types, required, allowed values) of one endpoint.

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": {
      "name": "<name>"
    },
    "name": "get_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesEndpoint name returned by search_endpoints, e.g. amazon_product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description contributes useful disclosure of what is returned (names, types, required, allowed values), which matters since there is no output schema, but says nothing about failure behavior for unknown endpoint names.

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?

A single front-loaded sentence with no filler, and the parenthetical enumerates return facets compactly. It is arguably a touch terse given the tool's role, but nothing is wasted.

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

Completeness4/5

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

For a one-parameter read tool with full annotation coverage, the definition is largely sufficient: it tells the agent what it gets back, which compensates for the missing output schema. The remaining gap is the absent tie-in to the call_endpoint workflow that this tool exists to support.

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

Parameters3/5

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

Schema coverage is 100%, and the single 'name' parameter is already documented in the schema as coming from search_endpoints. The description only restates 'one endpoint' and adds no format, casing, or error semantics beyond what the schema provides.

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 uses a specific verb ('Returns') plus a clearly bounded resource ('the description and parameters of one endpoint') and even enumerates the returned parameter facets. It does not explicitly name or contrast with search_endpoints or call_endpoint, so the sibling distinction is only indirect.

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

Usage Guidelines3/5

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

The intent (inspect an endpoint's shape) is implied rather than stated, and there is no explicit 'use this before call_endpoint' or 'do not use to list endpoints, use search_endpoints instead' routing. Usage is inferable from the return content but never spelled out.

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