Skip to main content
Glama

TrueInterview

Get my prep plan

get_prep_plan
Read-onlyIdempotent

What the candidate should practise next, in order: due revision, prep for employers in their pipeline and weak-topic practice, from the same engine as their study plan. With company, the plan's picks for that employer come first, topped up from what that employer asks most when the plan has too few (from says which). Returns links and a reason for each, never question text.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
companyNoFocus on one employer, e.g. "Stripe".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, and the description still adds real context: the deterministic ordering engine shared with the study plan, the top-up fallback when an employer has too few plan items, and the presence of a `from` marker indicating source. It also discloses output substance (links plus a reason per item, no question text). It does not mention pagination, empty-plan behavior, or the limit ceiling.

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?

Three sentences, front-loaded with the core answer and progressing to the company branch and the return contract. It is dense but nearly every clause carries information; the top-up sentence ('topped up from what that employer asks most when the plan has too few') is the one clause that reads awkwardly and costs a point.

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 usefully compensates by stating what comes back (links, a reason each, no question text) and what the `from` field signifies. For a two-parameter read-only tool this covers most of what an agent needs; the unmentioned `limit` cap and the behavior on an empty or brand-new account are the remaining gaps.

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 only 50%, so the description must carry some weight. It richly explains the `company` parameter's effect on ordering and fallback, adding meaning beyond the schema's 'Focus on one employer' note. But the `limit` parameter (default 8, maximum 15) is never mentioned, leaving half the parameter surface undocumented in both places.

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 (the prep plan) and specifies its composition and ordering: due revision, pipeline-employer prep, then weak-topic practice. It also distinguishes the output shape from question-search siblings by stating it returns links and reasons, 'never question text'. It stops short of naming a specific sibling to contrast with, so it is clear but not maximally differentiating.

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 implied by 'What the candidate should practise next', which tells an agent the intent, and the company clause explains the branch when an employer focus is wanted. However, there is no explicit statement of when to prefer this over get_my_progress or search_questions, and no exclusion guidance for cases where a plan is not appropriate.

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