Skip to main content
Glama

sport_sites

Retrieves the venue list and booking availability for a specified sports scene and date, including the server-provided reason when a site cannot be booked.

Instructions

某场馆场景某日的场地列表与可约状态(不可约时给服务端原因)。

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": {
      "scene": "<scene>"
    },
    "name": "sport_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo日期 YYYY-MM-DD(缺省明天)。
sceneYes场景名(子串)或 uuid,先用 sport_scenes 查。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description bears the full behavioral burden. It does disclose one valuable trait beyond the obvious: unavailable slots return a server-side reason ('不可约时给服务端原因'), which tells the agent not to treat unavailability as an error. It says nothing about read-only semantics, permissions, or whether the call is safe to repeat, leaving real gaps for an un-annotated tool.

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 compact clause pair that leads with the resource and appends the availability caveat in parentheses; there is no filler. It is efficient and front-loaded, though the parenthetical could be promoted to make the unavailability behavior more prominent.

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-parameter read tool with no annotations and no output schema, the description covers the purpose and one behavioral detail (server-side reason for unavailable slots). It omits the relationship to sport_scenes/sport_days/sport_reservations and what a result entry contains (time slots, pricing), which the missing output schema would otherwise have to carry.

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%, so both parameters are already fully documented in the schema, including the date default (缺省明天) and the '先用 sport_scenes 查' lookup hint. The description only restates that the call is scene- and date-scoped, adding essentially no semantics beyond the schema. Baseline 3 applies.

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 states a specific resource ('场地列表', venue/court list) scoped by two qualifiers ('某场馆场景', '某日') and adds what the response conveys ('可约状态'). An agent can tell this is a per-day availability listing rather than a booking action. It stops short of naming how it differs from siblings like sport_scenes or sport_days, so it is clear but not sibling-differentiating.

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 framing '某场馆场景某日的' implies the tool is used to check availability for a scene on a date, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives. The useful routing hint ('先用 sport_scenes 查') lives only in the schema, not the description. Usage is therefore only inferable from the phrasing.

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