Skip to main content
Glama

Progress

get_progress
Read-only

Practice statistics for the current language pair: today, the last N days, total, stories in review and due now.

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

Input Schema

NameRequiredDescriptionDefault
daysNoDefault 7.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds the useful behavioral fact that results are scoped to the current language pair rather than all languages. Because there is no output schema, the enumeration of returned metrics (today, last N days, total, in review, due now) meaningfully discloses what comes back. It does not cover staleness, caching, or how the N-day window interacts with the 'today' figure.

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?

A single front-loaded sentence with zero filler, but the colon-separated list of five metrics is slightly ambiguous — an agent must parse whether 'total' and 'due now' are separate figures or modifiers. Still efficient and well within acceptable length.

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?

For a one-optional-parameter read tool with no output schema, the description is nearly self-sufficient: it names the scope and the metrics returned. Remaining gaps (units/format of the statistics, behavior when no practice has occurred, whether 'total' is all-time) are minor but real.

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 'days' parameter is documented ('Default 7.'). The description only restates it as 'the last N days' without clarifying the default value or allowed range, so it adds no semantics beyond the schema. Baseline 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?

States a specific verb and resource (practice statistics) and scopes it to the current language pair, then enumerates the metrics covered. It is clear what the tool does, but it never names a sibling, and its scope ('stories in review and due now') visibly overlaps get_due_reviews and get_daily_stories without resolving the choice.

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?

Usage is only implied: 'practice statistics for the current language pair' suggests a dashboard/summary call, but there is no explicit when-to-use, no when-not, and no routing to get_due_reviews despite overlapping content. An agent can guess, but must infer the boundary itself.

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