Skip to main content
Glama

Orbit

by ai.buildwithorbit
OverviewDiscussionsAdmin

search

Find and evaluate public API endpoints and MCPs 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 (endpoint or mcp), name, description, method (for an endpoint) or transport (for an mcp), url, and evaluateGuide — an evaluation of what the endpoint or MCP 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.

Best practices for querying:

  • Use focused keyword queries that include the product or provider name along with the endpoint details, for example "PayPal create invoice".

  • Alternatively, use natural language queries such as "PayPal API to create an invoice".

  • Avoid jumbled queries that cram many unrelated keywords into a single query, for example "paypal invoice payment delivery payments ordering".

  • Avoid OR-separated queries such as "paypal invoice OR paypal create invoice OR paypal OR invoice creation".

  • If you need to explore multiple intents, try each as a separate call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesFree-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.
limitNoResults per page (default 10, max 25).
cursorNoPagination cursor from a prior response's `meta.nextCursor`. Omit for the first page.
clientNameNoName of the client application or agent invoking this tool (e.g. "cursor/composer-2.5", "claude/sonnet-4.6", "codex/gpt-5.6-sol"). Used for anonymous usage analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / clientName
      Added value: +{
+  "description": "Name of the client application or agent invoking this tool (e.g. \"cursor/composer-2.5\", \"claude/sonnet-4.6\", \"codex/gpt-5.6-sol\"). Used for anonymous usage analytics.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[^\\r\\n]+$",
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries full burden. It discloses key behavioral traits: matching by meaning and keyword, the structure of each result (including `evaluateGuide`), pagination mechanics (`cursor` from `meta.nextCursor`, limit defaults, max 25, stops at 40 results total), and no authentication required. This is comprehensive behavioral transparency beyond what any annotation might have provided.

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 long but well-organized. It front-loads the core purpose and result structure, then provides a clearly labeled best-practices section. Every sentence adds relevant information (result fields, pagination, no-auth, query examples). Slight redundancy exists between the schema and description for `limit`/`cursor`, but it's minimal and arguably reinforcing. Overall efficient for the tool's complexity.

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?

Given the tool's moderate complexity (search, pagination, result evaluation, integration routing) and absence of an output schema, the description is remarkably complete. It explains return fields, how to use `evaluateGuide` to select results, pagination limits, and even query best practices. An agent has everything needed to call it correctly and interpret results. No significant gaps.

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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying semantic nuances: `q` can be natural language, keywords, or a question; pagination stops at 40 total results; `clientName` is used for anonymous analytics. This extra context justifies a 4 rather than the baseline 3.

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?

The opening sentence states a specific purpose: 'Find and evaluate public API endpoints and MCPs that match your query.' It clearly identifies the resource (endpoints/MCPs) and the action (find and evaluate). It also distinguishes itself from the sibling `integrate` by explicitly stating 'pass each chosen result's `id` and `resourceType` (as `type`) to `integrate`.' No ambiguity.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use and how-to-use guidance. It explains when to use this tool (to explore and evaluate) and then route to `integrate` for actual integration. It also provides concrete best practices and anti-patterns for query formulation (e.g., avoid jumbled or OR-separated queries), making usage conditions clear.

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

All Orbit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources