Skip to main content
Glama

sport_days

Check daily availability and booking reasons for a Westlake sports venue by scene and site, with optional date range.

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>",
      "site": "<site>"
    },
    "name": "sport_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo结束日期 YYYY-MM-DD(缺省起始 +13 天)。
siteYes场地名(子串)或 uuid。
sceneYes场景名(子串)或 uuid。
startNo起始日期 YYYY-MM-DD(缺省今天)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does add genuine value by disclosing that swimming availability is frequently unavailable due to a missing server-side form rule, which prevents the agent from misreading empty results as 'fully booked'. However, it never states that this is a read-only query, nor what the per-day result shape looks like or whether unknown dates are omitted or marked unknown.

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 sentence with the core function front-loaded and the caveat bracketed off as secondary information. No redundant restatement of the name. It is perhaps too compact for its information density, but nothing is wasted.

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?

With no annotations and no output schema, the description must convey both safety profile and return semantics; it partially does the latter ('逐日可约状态与原因') but leaves the per-day record structure and empty-result behavior undefined. Adequate to attempt a call, incomplete for interpreting results, especially given the disclosed swimming data gap.

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 all four parameters are documented in-schema, including date defaults, so the baseline is 3. The description adds nothing about parameter behavior — notably it says '某场地' but never explains how scene and site interact, or that scene is required at all despite appearing unrelated to a venue-level query.

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 and output shape: per-day reservability status and reasons for a given venue ('逐日可约状态与原因'). An agent can tell this is a day-by-day availability query rather than a booking action, which implicitly separates it from sport_reservations. It stops short of naming the sibling tools (sport_scenes / sport_sites) it likely depends on for scene/site identifiers.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no mention of alternatives such as sport_reservations or sport_sites. The parenthetical about swimming is a data-reliability caveat, not a routing rule. The agent must infer from the required scene+site params that lookups must be preceded by an index/site search.

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