Skip to main content
Glama

Find integrations for a buyer

find_integrations

Find apps that integrate with an ecosystem, filtered and ranked for a buyer profile per Lode ranking policy (fit, not size or features). Returns score, match reasons and ties. Only published (verified) records are ranked; records still under review can be fetched by id with get_integration.

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": {
      "ecosystem": "<ecosystem>"
    },
    "name": "find_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
needsNoSync objects the buyer must have, from the ecosystem vocabulary (see list_ecosystems), e.g. ["invoices","inventory-levels"]
regionNoBuyer region; filters to apps that support it and prices in local currency
categoryNoCategory slug, e.g. "inventory", "crm", "payroll"
ecosystemYesEcosystem slug, e.g. "xero"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the ranking policy (fit-based, not size or feature count), that only verified published records are ranked, and that it returns score, match reasons and ties. It omits pagination/auth/permission behavior, and the 25-item cap is only in the 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?

Three sentences, each earning its place: purpose first, then behavior/ranking policy, then the routing constraint to the sibling tool. No filler or restatement of the title.

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?

There is no output schema, and the description compensates by naming the returned fields (score, match reasons, ties). For a five-parameter filtered-search tool that is nearly complete; only the result-set cap/pagination behavior, already implied by the schema limit, is left unstated.

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 80%, so the schema already documents ecosystem, needs, region and category, including the vocabulary pointer to list_ecosystems. The description adds only the framing that filtering is 'for a buyer profile' with fit-based ranking, not per-parameter format or interaction detail. Baseline 3 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?

Specific verb+resource: 'Find apps that integrate with an ecosystem, filtered and ranked for a buyer profile.' It goes further than the name by stating the ranking criterion ('fit, not size or features') and scoping to published records, which separates it from get_integration for the same domain.

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?

Explicit exclusion-and-alternative routing: published records are ranked here, while records 'still under review can be fetched by id with get_integration.' That is a real when-not rule. It does not address how this relates to compare_integrations or list_ecosystems (the latter only implied via schema), so the guidance is strong but not exhaustive.

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