Skip to main content
Glama

Get integration facts

get_integration

Get the full verified record for one app + ecosystem pair: what syncs, pricing by currency, regions, requirements, limitations, connection safety, sources.

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": {
      "id": "<id>"
    },
    "name": "get_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIntegration id "{app}--{ecosystem}", e.g. "shopify--xero"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden, and it does enumerate the returned data categories (sync behavior, pricing by currency, regions, requirements, limitations, connection safety, sources) — valuable since no output schema exists. It does not address error behavior, staleness/caching, or rate limits, and only implies read-only via the verb 'Get.'

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?

A single sentence with the action and scope front-loaded, followed by a compact colon-separated list of record contents. Every segment conveys information; there is no filler 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?

For a one-parameter lookup with no output schema, the description sufficiently covers what the call returns and what the id represents. Minor gaps remain around how to discover ids and whether records can go stale, but nothing essential for calling the tool correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the id parameter already documents the "{app}--{ecosystem}" format with an example. The description reinforces the app+ecosystem framing but adds no format or validation detail beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource: "Get the full verified record for one app + ecosystem pair." The follow-up list of record contents sharpens what 'full verified record' means. It does not explicitly contrast with siblings like find_integrations or compare_integrations, so it falls just short of 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 Guidelines3/5

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

Usage is implied by the phrase 'one app + ecosystem pair,' which signals a single-item lookup rather than a search or comparison. However, there is no explicit when-to-use statement, no mention of prerequisites (e.g., that an id must first be obtained from find_integrations), and no named alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources