Skip to main content
Glama

check_timeline

Convert relative day offsets into calendar dates and mark each registration timeline item as completed, in progress, not started, or overdue using a specified as-of date.

Instructions

把相对天数展开成日历日期,并按 as_of 标出 completed/in_progress/not_started 与逾期未启动项。

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

Input Schema

NameRequiredDescriptionDefault
as_ofNo判定基准日 YYYY-MM-DD(默认今天)
regionNo地区码,默认 CN
procedureNo程序名,默认 骨科植入物注册
start_dateNo起始日 YYYY-MM-DD(默认今天)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add genuine behavioral content by enumerating the status taxonomy, including the overdue-not-started bucket, which is not derivable from the input schema. However it says nothing about whether the tool is read-only/stateless, whether anything is persisted, or how results are shaped.

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 dense sentence with the main action ('expand relative days into calendar dates') front-loaded before the secondary status labeling. No filler, though the two clauses are packed into one sentence where a light break would aid scanning.

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?

Four optional parameters, no output schema and no annotations, so the description must do more work than it does. It omits where the relative-day data comes from given region/procedure, and gives no sense of the return shape for a tool whose entire value is a computed status table.

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?

Schema description coverage is 100% and every parameter already documents its format and default, so the baseline of 3 applies. The description adds a little extra meaning by tying as_of explicitly to the status determination (it is the judgment baseline, not just a date).

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 names a specific computation: expanding relative day offsets into calendar dates and labeling each item completed/in_progress/not_started or overdue-not-started relative to as_of. That is concrete enough to distinguish it from siblings like calc_quote or report_gap. It stops short of a 5 because it never says what timeline it reads from — the source of the 'relative days' is only inferable from the region/procedure parameters.

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 or when-not-to-use guidance and no named alternative. The agent can guess it is the scheduling/status tool, but nothing states the conditions under which this is the right choice versus check_udi or report_gap, nor any prerequisite (e.g. that a procedure template must exist).

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