Skip to main content
Glama

get_progress_summary

Read-onlyIdempotent

Summarize your most recent completed interviews: average score (0-100), trend, per-skill averages (0-10), and weakest topics, with links to each report. Reads saved reports only and never generates one. Requires reports:read and interviews:read.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of your most recent completed interviews to include, 1 to 20. Omit for 10.
interviewTypeNoOptional exact interview type to include, for example system_design or dsa.

Output Schema

NameRequiredDescriptionDefault
noteYes
trendYes
recentYes
skillsYes
averageScoreNo
weakestTopicsYes
reportsAnalyzedYes
reportsUnavailableYes
interviewsConsideredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world behavior, and non-destructiveness. The description adds useful context beyond annotations: it reads saved reports only, never generates reports, and requires reports:read and interviews:read permissions.

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 concise and front-loaded with the core summarization purpose. Every sentence contributes useful information: outputs, read-only behavior, and required scopes.

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?

Given the output schema, annotations, and fully documented parameters, the description supplies enough context for an agent to call the tool correctly. It also clarifies read-only behavior and required permissions, which are important operational constraints.

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 description coverage is 100%, so both parameters are already well documented in the input schema. The description does not add extra parameter meaning beyond what the schema provides, making the baseline score appropriate.

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 states a specific verb and resource: summarize recent completed interviews, including average score, trend, per-skill averages, weakest topics, and report links. It is clearly distinguishable from single-report and list-oriented siblings, but it does not explicitly name any sibling tool.

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?

It provides some usage context by saying it reads saved reports only and never generates one, which rules out creation workflows. However, it does not explicitly state when to use this tool versus get_interview_report, list_interviews, or search_mock_interviews.

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