Skip to main content
Glama

Vocab Voyage

by io.github.jaideepdhanoa

get_class_standing

Read-onlyIdempotent

Use this when a signed-in student asks how they're doing in their tutor class, who's ahead, who their rival is, or who they should challenge. Auth-only. Returns weekly XP rank inside the user's tutor class plus a winnable rival suggestion (similar weekly XP). NEVER name the class leader unless the user is rank #1 — the response uses '(top student)' as a deliberate placeholder. Renders the interactive class-standing widget on supporting hosts; falls back to markdown elsewhere. Anonymous callers receive a sign-in prompt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A5/5.0
Behavior5/5

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

Annotations indicate read-only and idempotent, but description adds key details: auth-only, return content (weekly XP rank, rival suggestion), deliberate placeholder for leader, rendering behavior. No contradiction.

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?

Four sentences that are complete and efficient. Front-loaded with usage, then auth, output, rendering. No wasted words.

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?

Covers all aspects: usage, auth, return value with components, behavioral rule, rendering, anonymous fallback. No output schema needed as description explains return values sufficiently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist; description explains all behavior meaningfully. Schema coverage is 100%, and description compensates fully by detailing what the tool does without needing inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies exact use cases ('how they're doing, who's ahead, rival, challenge') and distinguishes from siblings like get_my_progress or get_session_detail by focusing on class standing and rivalry.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use scenarios, auth requirement, and behavioral rule about naming the class leader. Also notes anonymous caller handling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vocab Voyage toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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.

Resources