Skip to main content
Glama

Run interview practice

manage_interview_practice
Destructive

Practice interviews (needs an Applystead membership): create, change and delete setups and questions, and start, answer, finish, score and delete practice sessions. Actions: create_setup, update_setup, delete_setup, create_question, update_question, delete_question, start_session, answer, finish_session, cancel_session, score_session, delete_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": "manage_interview_practice"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotency, so the safety profile is covered. The description adds value beyond that by disclosing the membership prerequisite and by making the destructive surface legible (three delete_* actions plus cancel_session) and by pointing at the help action for field-level detail. It does not say whether deletions are permanent or cascading, which would be the remaining gap.

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?

Front-loaded and dense: purpose, prerequisite, and the help mechanism all land early. The cost is the inline list of twelve action names, which repeats the schema enum and could have been compressed to "see the action enum".

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?

For a 13-action dispatcher with no output schema, the description covers the mutation surface, the auth prerequisite, and where to get per-action field documentation, which is enough for an agent to begin. What is missing is any hint about what start_session/score_session return and whether deletes are irreversible, which matters for a destructiveHint tool.

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 80% and the three id parameters already document their source (overview arrays, start_session return). The description's only added meaning is the help-action escape hatch for the nested params object, which largely restates the schema's own params description; the long action enumeration duplicates the enum verbatim.

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 uses a specific verb+resource ("Practice interviews") and enumerates the full action set, so an agent can see this is the write/mutation counterpart to the read-only get_interview_practice. It stops short of naming get_interview_practice explicitly, so the sibling differentiation is inferable rather than stated.

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?

"Needs an Applystead membership" is a genuine prerequisite and "call with action 'help'" is a useful procedural pointer. However, there is no explicit guidance on when to use this tool versus get_interview_practice (overview/read) or the other manage_* siblings, so routing must be inferred from the action names.

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.