Skip to main content
Glama

HSK test dates

exam_dates
Read-onlyIdempotent

List upcoming HSK test dates with registration deadlines and result dates, each with a link to its source notice. Dates can change; tell the user to confirm with their test center.

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

Input Schema

NameRequiredDescriptionDefault
levelsNoFilter by test band

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for the extra context it supplies: the volatility of the data ('Dates can change') and the follow-up instruction to have the user confirm with their test center. It does not mention ordering of results or whether past dates are excluded beyond the word 'upcoming'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is returned and ending with the caveat that matters most to the end user. No redundant restatement of the title or of annotation-declared properties.

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 single-parameter, read-only lookup with no output schema, the description covers what is returned, the presence of source links, and the caveat about changing dates. Nothing an agent needs in order 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 single optional 'levels' parameter carries an enum with a clear description ('Filter by test band'), so the schema does the work. The description adds nothing about filtering behavior or what omission of the parameter implies, which is the expected baseline when the schema is complete.

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?

Uses a specific verb ('List') plus a well-defined resource ('upcoming HSK test dates') and enumerates the returned fields (registration deadlines, result dates, source links). It is self-evidently distinct from all listed siblings (wordlists, quizzes, word lookup), though it never explicitly notes that separation.

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?

Usage is only implied by 'upcoming' — the agent can infer it should call this when asked about test scheduling. There is no explicit statement of when to call it, no prerequisites, and no named alternatives (none of the siblings overlap, so the practical gap is small).

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