Skip to main content
Glama

list_integrations

Read-only

List integrations (banks, payments, payroll, time tracking, shipping, accounting sync, ecommerce, CRM).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by rollout status.
countryNoOnly return integrations available in this country (or global).
categoryNoFilter to one integration category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds the domain range of the catalog, but says nothing about result size, ordering, pagination, or whether filters combine with OR/AND — with annotations carrying the safety profile, a 3 is appropriate.

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?

A single front-loaded sentence with the verb first and no filler. The parenthetical category list partially duplicates the category enum in the schema, which is mild redundancy but also useful at a glance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read-only listing tool with fully described params and annotations, the description covers purpose adequately. It is missing only routing guidance (when to use this versus check_integration) and any hint about result volume, which keeps it at minimum-viable rather than complete.

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 description coverage is 100% and all three parameters are self-documenting enums (status, country, category), so the schema does the heavy lifting. The description does not add filter syntax or semantics such as how country interacts with "global" entries, so it sits at the baseline.

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?

States a specific verb and resource ("List integrations") and enumerates the domains covered (banks, payments, payroll, shipping, CRM, etc.), which tells an agent what kind of catalog this returns. It does not explicitly distinguish itself from catalog siblings like list_api_catalog or check_integration, keeping it below 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 Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no pointer to the related check_integration sibling for looking up a specific integration. Usage is only implied by the verb "list".

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