Skip to main content
Glama

TrueInterview

Report a TrueInterview MCP problem

report_mcp_issue

Tell the TrueInterview MCP maintainers that one of its tools failed, returned something wrong, was missing or was confusing. Call it only when a TrueInterview tool itself got in the way (an unavailable error that persists, an answer that contradicts itself), at most once per task; a not_found, invalid_request or rate_limited answer is the tool working. It goes to the maintainers, not to the user's account, and stores nothing: leave out the user's personal details.

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": {
      "task": "<task>",
      "kind": "<kind>",
      "impact": "<impact>",
      "description": "<description>"
    },
    "name": "report_mcp_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesbroken: a tool failed or answered wrongly; missing: no tool could do it; confusing: a tool or its description was unclear; idea: a suggestion.
taskYesWhat the user asked you to do, in a short phrase.
impactYesblocked: you could not finish; worked_around: you finished another way; friction: it was harder than it should be.
tool_nameNoThe TrueInterview tool it is about, if one.
descriptionYesThe calls you made, with their arguments and what came back, and what went wrong.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare the write-shaped, non-destructive, non-idempotent profile; the description adds the destination ('goes to the maintainers, not the user's account'), the storage claim ('stores nothing'), the privacy instruction, and the once-per-task throttle. It does not say what acknowledgment or follow-up the agent gets after submitting, so not a 5.

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?

Purpose is front-loaded in the first sentence, followed by the gating condition, then recipient/privacy constraints. Dense but every clause carries a distinct rule; the long parenthetical could be split for easier scanning, which keeps it short of a 5.

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 5-parameter write tool with no output schema, the description covers the calling condition, exclusions, rate limit, destination and privacy, which is nearly all an agent needs to call it correctly. The remaining gap is post-submission behavior (confirmation, whether the user should be told), which is left implicit.

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% with enum meanings spelled out, so the baseline is 3. The description still adds decision-relevant meaning by classifying error classes as 'the tool working' — which directly steers the kind/impact choice away from broken/blocked — plus the instruction to omit personal details from the free-text description field.

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 and resource ('Tell the TrueInterview MCP maintainers that one of its tools failed...') and enumerates the failure modes covered: failed, wrong result, missing, confusing. It is distinguishable from the other report_* siblings because it names a different recipient (the maintainers, not the user's account).

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

Usage Guidelines5/5

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

Gives an explicit positive trigger ('only when a TrueInterview tool itself got in the way'), concrete examples (persistent unavailable error, self-contradicting answer), an explicit exclusion ('not_found, invalid_request or rate_limited is the tool working'), and a frequency cap ('at most once per task'). Nothing is left to inference.

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