Skip to main content
Glama

Talkhao

My Talkhao progress

my_progress
Read-onlyIdempotent

The signed-in learner's Talkhao progress by HSK level: words learned, words being learned, words not started and reviews due today. Give one HSK level (1-6), or none for the learner's own level and every level they have started. Needs the learner's Talkhao account connected.

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

Input Schema

NameRequiredDescriptionDefault
levelNoAn HSK level, 1-6. Leave it out for the learner's own level and every level they have started

Output Schema

NameRequiredDescriptionDefault
dueYesReviews due today across HSK 1-6, as Talkhao shows it
levelYesThe learner's HSK level
levelsYesThe level asked for, else the learner's and every started one
review_urlYesWhere the learner reviews on Talkhao
level_chosenYesWhether the learner chose it (else Talkhao suggests it from practice)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely new context beyond those annotations: that a connected Talkhao account is required, which is a prerequisite the agent cannot infer from structured fields.

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?

Two sentences with no filler; the resource and reported metrics are front-loaded and the usage/auth constraints follow. The second sentence packs both parameter behavior and the account prerequisite together, which is slightly dense but still efficient.

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 an output schema present and full schema coverage on the lone optional parameter, the description does not need to explain return values, and it correctly focuses on scope and the account prerequisite. Remaining gaps are minor, such as whether the figures are computed live or cached, but nothing essential to correct invocation 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 description coverage is 100% and the single optional parameter already documents the 1-6 range and null default in the schema itself. The description restates that same behavior with a small added nuance about 'every level they have started', but adds little beyond the schema text, so the baseline of 3 applies.

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 resource (the signed-in learner's Talkhao progress) and enumerates exactly what is reported: words learned, words being learned, words not started, and reviews due today. This clearly separates it from siblings like hsk_words or look_up_word, which deal with word data rather than the learner's own aggregate state, though no sibling is named explicitly.

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 explains the parameter choice (one HSK level 1-6, or omit for the learner's own level plus every started level), which implies when to use each form of the call. It offers no guidance on when this tool should be preferred over alternatives such as hsk_words, nor any exclusions or prerequisites beyond account connectivity.

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