Skip to main content
Glama
Sign In
Piloterr MCP Server

Piloterr MCP Server

Official
by piloterr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search Piloterr endpoints

search_endpoints
Read-only

Search 391 Piloterr endpoints by website, keyword, or path to find endpoint names for use with get_endpoint and call_endpoint.

Instructions

Search the 391 Piloterr endpoints by website, keyword or path (for example "amazon", "linkedin job", "zillow"). Returns endpoint names to use with get_endpoint and call_endpoint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 25).
queryNoWords to look for in the endpoint name, path or description. Omit to list everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description adds genuine context beyond them: the catalog size (391 endpoints) and the return shape (endpoint names, not full definitions), which matters because there is no output schema.

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?

Two sentences, front-loaded with the verb and scope; the examples are embedded inline rather than adding a separate paragraph. Nothing is wasted and the next-step guidance closes the sentence usefully.

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?

For a two-optional-parameter read-only search with full schema coverage and no output schema, this contains everything needed: what it searches, what it returns, and which tools consume the result. Further detail would be redundant.

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% and the schema documents both parameters including the default limit of 25. The description still adds value with concrete query examples ("amazon", "linkedin job", "zillow") that show query accepts company/brand names and multi-word phrases, which the schema's generic wording does not convey.

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?

States a specific verb (search) plus the exact resource (the 391 Piloterr endpoints) and the searchable dimensions (website, keyword, path). It also names the downstream siblings get_endpoint and call_endpoint, so an agent can place it in the workflow without opening any schema.

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?

Clear usage context: this is the discovery step that produces endpoint names for get_endpoint and call_endpoint. No explicit when-not or exclusions are given, but the routing to siblings makes the intent unambiguous.

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