Skip to main content
Glama
Sign In
Piloterr MCP Server

Piloterr MCP Server

Official
by piloterr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Call a Piloterr endpoint

call_endpoint
Read-only

Run one Piloterr web scraping endpoint with its required parameters to get structured JSON results; inspect parameters first because each call uses credits.

Instructions

Calls one Piloterr endpoint with its parameters and returns the result. Each call consumes credits. Use get_endpoint first to learn the parameters.

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": "call_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesEndpoint name, e.g. amazon_product.
paramsNoParameters as documented by get_endpoint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The description adds context the annotations do not carry: every call consumes credits, which is a cost/side-effect disclosure that materially affects invocation decisions. It also explains the indirect parameter source via get_endpoint. It says nothing about failure modes or response shape, but the credit-cost warning is the key non-obvious trait.

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

Conciseness5/5

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

Three short sentences, each carrying distinct information: what it does, what it costs, and what to do first. Front-loaded and free of filler.

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 generic endpoint proxy with only two parameters and no output schema, the definition covers purpose, cost, and the required prerequisite call, which is enough to invoke it correctly. A note on error behavior or whether results are cached would close the remaining gap.

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 the baseline is 3, but the description earns more by explaining that `params` is not a fixed set — it is whatever get_endpoint documents for the chosen `name`. That clarifies the free-form nested object in a way the schema's "Parameters as documented by get_endpoint" only partially implies.

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?

"Calls one Piloterr endpoint with its parameters and returns the result" gives a specific verb (calls) and resource (a named Piloterr endpoint), which clearly separates it from get_endpoint (metadata lookup) and search_endpoints (discovery). It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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

Usage Guidelines4/5

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

The sentence "Use get_endpoint first to learn the parameters" states a concrete prerequisite and routing rule, which is exactly the guidance an agent needs before invoking a dynamic proxy tool. It does not mention when to prefer search_endpoints or what to do if the endpoint name is unknown, leaving a small gap.

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