Skip to main content
Glama

List sourced aliases

list_aliases
Read-onlyIdempotent

Sourced trade and former names, served by the MCP of the issuer's home market.

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": {
      "identifier": "<identifier>"
    },
    "name": "list_aliases"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a provenance detail by saying results are served by the issuer's home-market MCP, but it does not explain return behavior, empty results, or permission needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and has no redundant wording, but it is a sentence fragment rather than a structured statement of what the tool does. The provenance clause is awkwardly placed and adds ambiguity as much as useful context.

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

Completeness2/5

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

For a one-parameter tool with no output schema and 0% schema description coverage, the description should clarify the identifier and the nature of the returned aliases. Instead it leaves the required input unexplained and gives only a cryptic statement about the source market.

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

Parameters2/5

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

The single required parameter 'identifier' has no schema description, and the tool description never mentions it. There is only a weak implication from 'issuer's home market' that the identifier relates to an issuer, with no accepted format or examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Sourced trade and former names' indicates the resource is trade names and former names, but it never states the action (listing/retrieving) explicitly. The added clause about being 'served by the MCP of the issuer's home market' is unclear and does not clarify purpose beyond the title.

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 guidance on when to use this tool, when not to use it, or which sibling tool to choose instead. The description implies an aliases lookup but does not give any context or conditions for invocation.

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.