Skip to main content
Glama

List Destinations Tool

list-destinations
Read-onlyIdempotent

List external data destinations for the space. Only the space owner and space admins may call this tool. Custom destinations return HTTP settings with secrets masked. Telegram and Google Ads destinations return preset_type and that type's settings. The Telegram bot token is masked and the raw Telegram URL is omitted.

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-destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceNoSpace slug. Required when the token is bound to more than one space. Omit it when the token has one space.

Output Schema

NameRequiredDescriptionDefault
destinationsYes
permission_noticeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The annotations only cover readOnlyHint and idempotentHint, so the description is the only place to learn behavior. It supplies exactly that: the description explains the permission gate, that secrets are masked, and that the raw Telegram URL is omitted. For a read-only listing operation exposed to potentially sensitive data, this level of disclosure is unusually strong.

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?

Four sentences, front-loaded with scope and permission before the per-destination-type return notes; nothing is padded. The only minor redundancy is the second mention of masking in the last sentence, which overlaps with the earlier "secrets masked" claim.

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

Completeness5/5

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

An output schema exists and the schema fully documents the single parameter, so the description does not need to restate return shapes. It still adds the pieces structured data cannot express: authorization scope and secret-masking behavior, which is complete for a read-only list tool.

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 parameter whose schema description already covers it at 100% of the parameters, including the conditional rule about when to supply the space slug. The prose in the description adds no further detail about the parameter, so the baseline score of 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?

"List external data destinations for the space" names a specific verb (List), a specific resource (external data destinations), and an explicit scope (the space). This is enough to distinguish it from the sibling list-* tools, which cover datasets, guides, projects, and reverse-ETL processes rather than destinations.

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?

The description gives a clear usage precondition: only the space owner and space admins may call it. It does not name alternatives or state when-not-to-use it, so it falls short of the 5 bar, but the authorization context is genuinely clear and actionable.

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