Skip to main content
Glama

List all the Integrations

get_details_of_all_integrations
Read-onlyIdempotent

List all the Integrations. Get the details of all Integrations available for the account Requires feature: integrations.

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": "get_details_of_all_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral fact is the account-level scope and the required `integrations` feature flag, which is genuinely useful prerequisite context, but it says nothing about result volume, pagination, or ordering.

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?

Two short sentences, front-loaded with the action and resource, with the feature prerequisite clearly flagged in bold. The first sentence largely restates the title and the second repeats the resource name, so there is minor redundancy, but nothing extraneous.

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 simple, read-only, single-optional-parameter list tool with no output schema and full annotation coverage, the description supplies the essential facts: what is listed, that it is account-scoped, and that a feature flag is required. The remaining gap, whether the result set is paginated or bounded, is minor at this complexity.

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?

There is a single optional `fields` parameter with 100% schema description coverage, so the schema already explains the projection behavior and enumerates allowed field names. The description adds no further meaning about the parameter, which is the expected baseline when the schema does the work.

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 all the Integrations', 'Get the details of all Integrations available for the account'), so the agent knows exactly what is returned. It does not distinguish itself from adjacent siblings such as list_crm_integrations, leaving the reader to infer the difference from names alone.

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 only implied: the tool returns the full set of integrations, and the 'Requires feature: integrations' note hints at a prerequisite. There is no explicit when-to-use versus when-to-use-an-alternative guidance, and no mention of how this differs from the CRM-integrations listing sibling.

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