Orbit

search

Find and evaluate public API endpoints that match your query. Set q to a natural language query, keywords, an API name, or a question — results are matched by meaning and keyword; each result includes id, resourceType, name, description, method, url, and evaluateGuide — an evaluation of what the endpoint does, when to use it, and its limitations. Review evaluateGuide to pick the best fit, then pass each chosen result's id and resourceType (as type) to integrate. Paginate with cursor from meta.nextCursor (limit defaults to 10, max 25; pagination stops at 40 results total). No authentication required.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	Free-text search: a natural language query, keywords, an API name, or a question (e.g. "weather forecast", "twilio", "Add tracking details for an existing paypal order"). Matched by meaning and keyword.
`limit`	No	Results per page (default 10, max 25).
`cursor`	No	Pagination cursor from a prior response's `meta.nextCursor`. Omit for the first page.

TDQS

A4.7/5.0

Behavior5/5

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

No annotations are provided, so description carries full burden. It discloses matching semantics (meaning and keyword), result structure, evaluateGuide contents, pagination behavior including the 40-result cap, and no authentication requirement.

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?

The description is dense but efficient; every sentence adds useful information. It front-loads the core purpose, then covers result fields, workflow, pagination, and auth in a logical order without redundancy.

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 search tool with 3 parameters, no output schema, and one sibling, the description is complete: it explains q semantics, how to evaluate results, pagination mechanics including limits, and the integration handoff. Nothing critical is missing.

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 meaningful context beyond the schema by explaining pagination stops at 40 results and the workflow for using result ids with integrate, augmenting what the schema already documents.

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?

Description states a specific verb and resource: 'Find and evaluate public API endpoints.' It clearly differentiates from sibling 'integrate' by describing the handoff workflow (pass result id/resourceType to integrate).

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?

Description clearly explains how to use the tool: set q to natural language, keywords, API name, or question; review evaluateGuide to select results; paginate with cursor. It implicitly routes to integrate for the next step, but doesn't explicitly state when not to use search.

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

All Orbit tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Search and integrate have clearly distinct roles: search discovers and evaluates endpoints, while integrate consumes selected search results to produce implementation details. The descriptions explicitly define the handoff between them, so there is no realistic confusion.

Naming Consistency5/5

Both tools use short, single-word imperative verbs: search and integrate. The naming style is consistent and predictable for a small, workflow-oriented tool set.

Tool Count4/5

With only two tools, the server feels intentionally minimal, but both tools are essential to the search-then-integrate workflow. The count is slightly small, yet well matched to the server's narrow purpose.

Completeness5/5

The server covers the full intended workflow: search paginates through public endpoints, evaluates candidates, and integrate converts selected resources into actionable integration guidance. There are no obvious dead ends or missing lifecycle steps for this domain.

Resources

Need Help?