Skip to main content
Glama

Read interview practice

get_interview_practice
Read-onlyIdempotent

Practice interviews (needs an Applystead membership): setups, sessions, scores and the question bank. Actions: overview, bank, get_session. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "get_interview_practice"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
session_idNoA practice session's id from get_interview_practice overview (sessions[].id) or manage_interview_practice start_session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description's added value is the membership requirement, a real access prerequisite not encoded in annotations or schema. It says nothing about result shape, volume, or pagination for the bank/overview payloads.

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 resource and its membership gate, followed by the action list and the help pointer. No filler, though the help pointer is duplicated in the schema's params description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should hint at what overview, bank, and get_session return; it only names the domains (setups, sessions, scores, question bank). The nested `params` object remains contentless in the description, and the help action is the only path to discovering required fields for an actual call.

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 67% and session_id is already fully documented there, including provenance from overview or manage_interview_practice. The opaque `params` bag is not explained beyond deferring to action "help", which is a reasonable escape hatch but adds no field-level meaning; the action enum is restated rather than enriched.

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 (practice interviews) and enumerates the read operations (overview, bank, get_session), so the agent knows what data domains are reachable. It does not explicitly frame it as a read tool or contrast it with the write sibling manage_interview_practice, so differentiation still relies on the tool name.

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 states a precondition (an Applystead membership is required) and points to action "help" for field details, which is useful routing. However, it never says when to choose this over manage_interview_practice, which performs the writes (start_session is referenced only inside the schema), leaving the use-vs-alternative decision implicit.

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.