mark_word_known
Idempotent
Manually mark a word as mastered for the signed-in user (same as the flashcard 'I knew this' override). Requires sign-in.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| word | No | ||
| card_id | No |
Vocab Voyage
TDQS
B3.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds the requirement of sign-in, which is not in the annotations. However, beyond that, it does not elaborate on mutability or idempotency. The idempotentHint and destructiveHint are already declared, so this is adequate but not exemplary.
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?
The description is extremely concise with two sentences, front-loading the core action. Every word serves a purpose without unnecessary detail.
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?
Given the tool has two optional parameters and no output schema, the description is somewhat complete in describing the action, but it omits parameter details and expected return values, which are needed for full understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description should clarify the two parameters. It fails to mention 'word' and 'card_id' at all, leaving the agent to guess their roles.
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 clearly states the tool marks a word as mastered for the signed-in user, analogous to the 'I knew this' flashcard override. However, it could more explicitly distinguish it from the sibling tool 'mark_word_difficult'.
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?
The description provides no guidance on when to use this tool versus alternatives like 'mark_word_difficult' or 'record_word_result'. It only mentions 'requires sign-in', which is a prerequisite, not a usage condition.
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.
TDQS
A3.7/5.0
Disambiguation4/5
Most tools have clear, distinct purposes with detailed descriptions. A few pairs like study_plan_preview vs get_study_plan_recommendation or get_definition vs explain_word_in_context have subtle overlaps, but descriptions effectively differentiate them.
Naming Consistency4/5
All tool names use lowercase snake_case with a consistent verb_noun pattern. Some names are longer but follow the same structure. No mixing of conventions, though the variety of verbs is high.
Tool Count3/5
31 tools is on the high side for a vocabulary server. The scope is broad (definition, quizzes, games, progress, parent/tutor features), but many tools are specific, making the set feel heavy. It earns its count but could be trimmed.
Completeness4/5
The tool surface covers most user needs: learning, testing, progress tracking, parental involvement, and support. Minor gaps like class management or deletion operations exist, but core vocabulary workflows are complete.