Skip to main content
Glama

sport_scenes

Lists all sports venue and swimming system scenes for Westlake University, clarifying that swimming and court bookings are handled outside the reservation center.

Instructions

体育场馆/游泳系统(正元 sportvenue)的全部场景;游泳与球场不在预约中心。

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": "sport_scenes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It gives no indication of read-only vs mutating behavior, whether results are static or live availability, pagination, or any auth/prerequisite context — only a scope claim.

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 short sentence with the domain qualification front-loaded and no filler. It is efficient, but the terseness comes at the cost of substance rather than trimming redundancy.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only source of behavioral information, and it omits what the call actually yields. For a zero-arg discovery-style tool the agent needs at least the nature of the return payload and its relationship to sport_sites/sport_reservations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema cannot be enriched; the baseline for a no-parameter tool applies. Nothing in the description misleads about inputs, though it also does not explain what the parameterless call keys on.

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 names the domain (体育场馆/游泳系统, 正元 sportvenue) but the operative noun is '全部场景' (all scenes), which never states what the tool returns or does — a list of venues, a scene catalog, a system tree? No verb or output type is given, so an agent cannot predict the response shape from the text alone.

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?

There is an implicit routing hint: swimming and sports fields are 'not in the booking center' (预约中心), which steers an agent away from sport_reservations for those cases. However, it never says when to use this tool instead of the explicit siblings sport_sites, sport_days, or sport_reservations, so the boundary remains guesswork.

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