Skip to main content
Glama

AceRound AI Interview Copilot

delete_question_prediction

Destructive

Delete a question prediction. The record ID comes from list_question_predictions. Used credits are not returned. Deletion cannot be undone; tell the user what will be deleted and get their agreement first. (Requires the user's sign-in with scope interviews:write.)

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": {
      "id": "<id>"
    },
    "name": "delete_question_prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPrediction ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: destructiveHint=true already flags irreversibility in spirit, but the description explicitly states 'Used credits are not returned' (a non-obvious side effect), 'Deletion cannot be undone', and the required auth scope 'interviews:write'. These are exactly the facts an agent needs before committing a destructive call.

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?

Four short sentences, front-loaded with the action, then provenance, then side effect, then the confirmation protocol and auth requirement. Nothing is redundant and no sentence could be dropped without losing decision-relevant information.

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?

For a one-parameter destructive tool with annotations covering the safety profile and no output schema, the description supplies everything else an agent needs: ID source, credit-loss consequence, irreversibility, human-confirmation step, and auth scope.

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?

Schema coverage is 100% and the schema's 'Prediction ID' is adequate, so the baseline would be 3. The description adds provenance — where the ID must come from (list_question_predictions) — which prevents the agent from guessing or fabricating an identifier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Delete a question prediction'), and the resource is unambiguous among the delete_* siblings (delete_exam, delete_interview, delete_knowledge_base, etc.). An agent can select this tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete prerequisite ('The record ID comes from list_question_predictions') and a procedural requirement ('tell the user what will be deleted and get their agreement first'). It does not name an alternative or exclusion, but for a deletion endpoint with a single entry path, the guidance is clear and actionable.

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