Skip to main content
Glama
Sign In

Corridome

by com.corridome
OverviewDiscussionsAdmin

List affiliations

list_affiliations
Read-onlyIdempotent

The broker-dealers firms say on their own websites they offer securities through, and the networks, associations and franchises they belong to, each with how many firms say so.

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

Input Schema

NameRequiredDescriptionDefault
kindNosecurities_through: broker-dealers firms say they offer securities through. network_member, association_member, franchise_office: networks, associations and franchises firms say they belong to.
queryNoPart of the broker-dealer's, network's, association's or franchise's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds that each result carries a count of how many firms report the affiliation, which is useful behavior beyond annotations, but it omits ordering, pagination, or empty-result behavior.

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?

It is a single sentence with no filler, but the phrasing is awkward and hard to parse, especially the repeated 'firms say' construction. The core idea is packed in, but readability suffers.

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 two-parameter read-only listing tool with no output schema, the description explains what a result represents and that it includes a firm count. However, it does not describe result shape, pagination, or ordering, leaving some gaps for an agent invoking the 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?

Schema description coverage is 100%, and both parameters are documented in the schema, including enum values and query constraints. The description loosely echoes the affiliation categories but adds no parameter meaning beyond what the schema already provides, so the baseline of 3 applies.

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 description identifies the resource as affiliations and says results include a count of firms, but it is a convoluted noun phrase rather than a clear verb-plus-resource statement. It implies listing, yet never explicitly distinguishes this from sibling tools such as get_affiliation or search_firms.

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 versus get_affiliation, search_firms, or other list tools. The only implicit usage signal is the word 'list' in the title, with no context about exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Corridome toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources