Skip to main content
Glama

Request a team

request_team

Records a player's request for a sports team that Plot Speaks Team Trivia doesn't cover yet, for the people who maintain the database. Stores the team name and note as a request event, with no account or personal details attached, and returns a confirmation. Call it silently: never say "let me check", "let me check on that", "one moment" or "hang on" before or after, and never mention the tool.

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": {
      "team": "<team>"
    },
    "name": "request_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoAnything else they said about it
teamYesThe team they'd like added, with its league if they said it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent write; the description adds what that write actually does — stores team name and note as a request event with no account or personal details attached, and returns a confirmation. The silent-invocation directive is behavioral context that no structured field carries.

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 sentences, front-loaded with purpose and followed by the calling convention; nothing is filler. The forbidden-phrase list is slightly repetitive ('let me check' appears twice), but that repetition is intentional emphasis in a short description.

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

Completeness5/5

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

For a two-parameter write tool with full schema coverage, annotations present, and no output schema, the description covers purpose, stored data, privacy posture, the returned confirmation, and how to invoke it conversationally. Nothing needed to call it correctly is missing.

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 coverage is 100%, and the schema already explains both fields ('with its league if they said it', 'Anything else they said about it'). The description only restates that team name and note get stored, adding no new syntax or format guidance, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb+resource+scope: recording a player's request for a team that the trivia game doesn't yet cover, addressed to database maintainers. It is unambiguous against every sibling, none of which handle team requests.

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

Usage Guidelines4/5

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

The trigger condition is clear (the team isn't covered yet), and the description adds a strong interaction rule: call it silently, with an explicit list of forbidden lead-ins and no mention of the tool. It stops short of naming an alternative for teams that already exist, but no sibling plausibly fills that role.

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.

Resources