Skip to main content
Glama

Talkhao

Save words to Talkhao

save_words
Idempotent

Save HSK words to the signed-in learner's Talkhao sets, so they come up in practice. Give the words in Chinese characters, up to 20. Supports bracketed headwords (e.g. 花(名词), 长(动词)) to disambiguate readings. Needs the learner's Talkhao account connected.

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": {
      "words": "<words>"
    },
    "name": "save_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordsYesThe words to save, in Chinese characters, up to 20. Supports bracketed headwords (e.g. 花(名词), 长(动词)) to disambiguate.

Output Schema

NameRequiredDescriptionDefault
savedYesHow many words were saved now
wordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, idempotent, closed-world write, so the safety profile is covered. The description adds useful context about the account-connection prerequisite and the practice effect, but it does not clarify which of the learner's sets are modified or how duplicate/ambiguous words are handled.

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?

The description is three front-loaded sentences that move from purpose to input constraint to prerequisite. It is efficient overall, though the 'up to 20' constraint and bracket examples are restated from the schema rather than adding new value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one fully described parameter, a present output schema, and annotations covering safety and idempotency, the description is close to complete. The main remaining gap is that it refers to 'Talkhao sets' without clarifying whether some or all sets are targeted and how existing entries are affected.

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 description coverage is 100%, so the schema fully documents the single 'words' parameter, including the 20-item limit and bracket syntax. The description largely repeats that same information ('Give the words in Chinese characters, up to 20' and the bracketed-headword examples) rather than adding new meaning beyond the schema.

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 uses a specific verb and resource: 'Save HSK words to the signed-in learner's Talkhao sets,' and adds the intended effect 'so they come up in practice.' It is clearly distinct from lookup or progress siblings, but it does not explicitly name alternative tools or explain why one would use it instead of them.

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 description states a prerequisite ('Needs the learner's Talkhao account connected') and implies the use case of adding words so they appear in practice. However, it gives no explicit when-not or alternative-tool guidance, and does not describe behavior when words already exist in the learner's sets.

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