Skip to main content
Glama

Talkhao

Stroke data

stroke_data
Read-onlyIdempotent

Stroke data for the characters on Talkhao's word card, for the card to draw them stroke by stroke.

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": {
      "characters": "<characters>"
    },
    "name": "stroke_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
charactersYesThe characters to draw, as written: a word such as 反馈

Output Schema

NameRequiredDescriptionDefault
missingNoCharacters asked for that have no stroke data
charactersYesIn the order asked, each character once

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered structurally. The description adds the rendering intent but says nothing about failure modes (e.g., invalid or non-CJK characters) or return format beyond what the output schema provides.

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?

One short, front-loaded sentence with no extraneous content. The trailing clause 'for the card to draw them stroke by stroke' slightly restates the purpose but does add the rendering goal.

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 an output schema present and full parameter coverage, the essentials are covered. However, for a data-fetch tool there is no mention of what the stroke data looks like conceptually or how it handles mixed/invalid input, leaving modest gaps.

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 parameter already documents its format with an example (反馈), so the description has no room to add parameter meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific resource – stroke data for given characters – and ties it to a concrete use (rendering a word card stroke by stroke). It is clearly distinct from siblings like look_up_word or hsk_words, though it doesn't name an alternative explicitly.

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?

No when-to-use or when-not-to-use guidance is offered. The phrase 'for the card to draw them stroke by stroke' hints at rendering purposes but gives no conditions, prerequisites, or alternatives an agent should weigh.

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