Skip to main content
Glama

get_participants

Read-only

Read verified event team participants with ESPN league-scoped IDs. No canonical cross-book identity.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes

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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful data caveat beyond the annotations — participants are 'verified' and IDs are ESPN league-scoped with 'no canonical cross-book identity' — but says nothing about return shape, pagination, or what happens when an event has no verified participants.

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 with the capability stated first and the identity caveat second; nothing is wasted. The phrase 'No canonical cross-book identity' is terse to the point of requiring inference, which costs a point on clarity.

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 one-parameter read tool with full annotation coverage there is no output schema, so the description should at least indicate what comes back and how participants relate to the event. It covers the ID-scoping pitfall well but leaves the return content and the event-scoping assumption unstated.

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 0%, so the description carries the burden of explaining the single event_id parameter, and it only indirectly does so via the phrase 'ESPN league-scoped IDs'. The schema's regex pattern does encode the 'espn-draftkings:espn:LEAGUE:id' format, but neither field states that the parameter must be that namespaced ID rather than a plain numeric event id.

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?

The description names a specific verb and resource ('Read verified event team participants') and scopes the data ('ESPN league-scoped IDs'), which lets an agent distinguish it from sibling get_participant. It stops short of stating exactly what a 'participant' is (team vs. player) or that results are scoped to one event, so the purpose is clear but not fully pinned down.

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 explicit when-to-use guidance and no named alternative, even though a near-identical sibling (get_participant) exists. The agent must infer from the event_id parameter that this is the per-event participant lookup, and has no stated condition for choosing between this and the singular 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.