Skip to main content
Glama

og_tournaments_by_id

Tournament OG card

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": {
      "region": "<region>",
      "id": "<id>"
    },
    "name": "og_tournaments_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTournament id.
regionYesGame server region.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.4/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: not read/write, not auth requirements, not rate limits, not what an 'OG card' contains. The description also fails to address mutation or side-effect behavior for a tool whose name suggests a fetch.

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

Conciseness2/5

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

It is short, but brevity here comes from under-specification rather than tight writing. A three-word fragment is not a front-loaded, informative description, so this is not 'conciseness' in the positive sense.

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

Completeness1/5

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

For a two-required-parameter tool with no annotations and no output schema, the description should explain the return shape, the meaning of 'OG', and the relationship to sibling tournament tools. It supplies none of that, leaving the definition effectively incomplete.

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%, with both id and region documented and region having an enum. Per the rubric, high schema coverage sets a baseline of 3, and the description adds nothing beyond the schema, so it neither helps nor hurts.

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

Purpose1/5

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

"Tournament OG card" is a fragment, not a statement of purpose. It restates the name (og_tournaments_by_id) without saying what the tool returns or how it differs from tournaments_by_id. An agent cannot determine the action or output from this text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as tournaments_by_id or og_tournaments_by_id_team_by_teamId. The 'OG' prefix is never explained.

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.