Skip to main content
Glama

Orbit

by ai.buildwithorbit
OverviewDiscussionsAdmin

integrate

Get integration details for public endpoints and MCPs from search results. Provide a task describing what you want to accomplish and up to 10 resources — each with an id and type taken from the matching search result's resourceType. Returns a task brief covering authentication, base URLs, request steps, parameters, expected responses, dependencies between steps, and other important considerations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesWhat you want to accomplish with the selected resources (max 512 characters).
resourcesYesUp to 10 endpoints or MCPs to integrate. Each entry needs an `id` and `type` from a search result (`type` is the result's `resourceType`).
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. Changed4 schema fields changed
    • changedInput schema / properties / resources / description
      Previous value: -"Up to 10 endpoints to integrate. Each entry needs an `id` and `type` from a search result (`type` is the result's `resourceType`)."New value: +"Up to 10 endpoints or MCPs to integrate. Each entry needs an `id` and `type` from a search result (`type` is the result's `resourceType`)."
    • changedInput schema / properties / resources / items / properties / id / description
      Previous value: -"Endpoint id from a search result's `id` field."New value: +"Resource id from a search result's `id` field."
    • changedInput schema / properties / resources / items / properties / type / description
      Previous value: -"Resource type from a search result's `resourceType` field."New value: +"Resource type from a search result's `resourceType` field (`endpoint` or `mcp`)."
    • changedInput schema / properties / task / description
      Previous value: -"What you want to accomplish with the selected endpoints (max 512 characters)."New value: +"What you want to accomplish with the selected resources (max 512 characters)."
  2. 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"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a task brief covering authentication, base URLs, request steps, parameters, expected responses, dependencies between steps, and other considerations. It also implies a read-only operation (getting details) and does not claim any destructive side effects. It could be more explicit about whether it performs any external calls or just compiles a brief, but the disclosed return content is substantial.

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 a single, dense paragraph that front-loads the core purpose and then details the required inputs and expected output. Every sentence earns its place: the first sentence states the function, the second explains the input format, and the third lists the output contents. No fluff or repetition.

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?

Given the tool's moderate complexity (3 params, no output schema, no annotations), the description is quite complete. It explains the input contract (task + resources from search results), the output contents (task brief with auth, base URLs, steps, etc.), and the relationship to the sibling tool. The only minor gap is that it doesn't explicitly state whether the tool makes external network calls or just synthesizes a plan, but the phrase 'task brief' suggests a synthesized document. Overall, it's sufficient for an agent to use correctly.

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 schema already documents all three parameters. The description adds value by explaining the relationship between `resources` and search results (`resourceType`), and by clarifying the purpose of `task` ('describing what you want to accomplish'). It also adds the constraint of up to 10 resources, which is already in the schema but reinforced. The description doesn't add much beyond the schema, but the schema is already rich, so a 4 is appropriate.

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 description clearly states the tool's purpose: 'Get integration details for public endpoints and MCPs from `search` results.' It specifies the verb (get), the resource (integration details), and the source (search results). It also distinguishes itself from the sibling tool `search` by explaining that it consumes search results to produce a task brief.

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 explicitly instructs the agent to provide a `task` and up to 10 `resources` with `id` and `type` taken from the matching search result's `resourceType`. It also names the sibling tool `search` as the source of these results, making the workflow clear: first search, then integrate. This is strong when-to-use guidance.

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