Skip to main content
Glama

TrueInterview

Get my practice progress

get_my_progress
Read-onlyIdempotent

The candidate's own practice record: questions solved, overall mastery, weakest measured topics and recent AI-review scores (overall only), and per active application how much of that employer's question list is solved. A topic with no practice signal is left out rather than shown as zero.

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_my_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is carried. The description adds genuine behavioral context beyond them: AI-review scores are 'overall only' (not per-question detail), and topics with no practice signal are omitted rather than reported as zero, which prevents misreading empty results as failure.

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, front-loaded with the returned data set and followed by a single caveat that earns its place by preventing a misreading of missing topics. The field enumeration is dense but readable; no filler or restatement of the title.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so field by field, including the per-application breakdown. What is missing is the response shape (nesting, ordering, whether 'weakest topics' is ranked), but for a zero-parameter read tool this is close to complete.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline of 4 applies. Nothing in the text misdescribes inputs, and the self-scoped nature ('the candidate's own') implicitly confirms no filtering arguments are needed.

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 the resource precisely ('The candidate's own practice record') and enumerates exactly what it contains: questions solved, mastery, weakest topics, AI-review scores, per-application coverage. That is far more specific than the title alone. It stops short of naming a sibling or stating what it is not, so 4 rather than 5.

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: an agent can infer this is the tool for reading its own practice/readiness state, and the 'per active application' phrasing hints at use before applying. There is no explicit when-to-use, when-not-to-use, or named alternative among siblings like get_my_conversation or report_setup_progress.

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