Skip to main content
Glama

See what this person has answered so far

my_progress
Read-only

Their recorded history for one exam, broken down by blueprint domain with the weakest first, plus how their misses compare with everyone else's on the same free-form questions. Call this at the start of a study session to decide what to drill, and after a run of questions to show what moved. It names the domain to pass to get_practice_question, and when their misses follow the crowd's favorite wrong answers it says to drill those with focus: "traps". Only a signed-in account has history; anonymous callers are told so rather than shown zeros.

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": {
      "exam": "<exam>"
    },
    "name": "my_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
examYesExam slug from list_exams.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / exam / enum
      Previous value: -[
      -  "ccar-p",
      -  "ccdv-f",
      -  "ccao-f",
      -  "ccar-f",
      -  "ccdv-p"
      -]New value: +[
      +  "ccar-p",
      +  "ccdv-f",
      +  "ccao-f",
      +  "ccar-f",
      +  "ccdv-p",
      +  "ccar-p-v2",
      +  "ccdv-f-v2",
      +  "ccao-f-v2"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / exam / enum
      Previous value: -[
      -  "ccar-p",
      -  "ccdv-f",
      -  "ccao-f",
      -  "ccar-f"
      -]New value: +[
      +  "ccar-p",
      +  "ccdv-f",
      +  "ccao-f",
      +  "ccar-f",
      +  "ccdv-p"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a read-only, closed-world operation, and the description adds disclosure the annotations cannot: only signed-in accounts have history and anonymous callers are told so instead of receiving zero-filled rows. That prevents a plausible misreading of the response. It does not cover volume limits or history depth, so it falls just short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and timing are front-loaded, but the third sentence compresses two unrelated ideas, naming the domain to pass along and recommending focus: "traps" for crowd-aligned misses, into one hard-to-parse clause. Splitting that and trimming the rhetorical framing would make it tighter without losing content.

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 no output schema, the description carries the return-value burden and does describe the shape: per-domain breakdown ordered weakest first plus a crowd-comparison signal. Together with the anonymity caveat and the handoff to get_practice_question, an agent has enough to call it and interpret the result, though ordering specifics and any empty-history case are not detailed.

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 exam parameter is documented as an exam slug from list_exams with an enum, so the description need not restate it. What the description adds about the exam argument is mostly indirect, via the returned domain feeding get_practice_question rather than anything new about the input itself. Baseline 3 is appropriate.

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 opening sentence names a specific resource (recorded exam history) and its scope (one exam, broken down by blueprint domain, weakest first, plus crowd comparison on free-form misses). That is distinguishable from get_practice_question or check_answer without opening any schema.

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?

It gives explicit call sites: at the start of a study session to pick what to drill, and after a run of questions to see what moved. It also routes forward to get_practice_question via the returned domain name and tells the agent when to use the focus: "traps" option, which is real when-to-do-what guidance rather than implied context.

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