Skip to main content
Glama

get_participant

Read-only

Read one verified team participant within the specified retained event; missing participants return404.

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>",
      "participant_id": "<participant_id>"
    },
    "name": "get_participant"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
participant_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 behavioral detail—missing participants yield a 404—plus the "verified"/"retained" qualifiers, but says nothing about the payload shape or whether results are cache-backed.

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?

A single front-loaded sentence with no filler; the scope constraint comes before the error behavior. Minor blemish: "return404" is run together, slightly hurting readability.

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-required-param read-one tool with no output schema and no annotated descriptions, the definition covers the key failure mode (404) but leaves the agent guessing at the returned participant fields and at how event_id and participant_id relate beyond the pattern prefixes.

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 schema contributes only regex patterns; the description partially compensates by tying participant lookup to an event and by calling the participant a "team" (matching the pattern's team: segment). It still does not explain the espn-draftkings:espn:<league>:<id> ID construction or the league-enum constraint beyond what the pattern shows.

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?

Uses a specific verb and resource: "Read one verified team participant," scoped to "the specified retained event." The word "one" implicitly separates it from the plural list sibling get_participants, and "team participant" clarifies the entity kind, though no sibling is named explicitly.

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?

The phrase "within the specified retained event" implies the tool is for single-entity lookups against already-retained/historical events, and "verified" hints at a filtering condition. However, there is no explicit statement of when to prefer this over get_participants or how to discover a valid participant_id first.

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.