Skip to main content
Glama

Get feedback on an interview answer

get_answer_feedback
Read-only

Gives feedback on one practice interview answer: a verdict (Strong, Good start or Needs work), what worked, the one thing to fix, and a stronger way to start the answer, shown as a feedback card.

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": {
      "role": "<role>",
      "question": "<question>",
      "answer": "<answer>"
    },
    "name": "get_answer_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesThe job the user is practising for.
answerYesThe user's answer, word for word.
questionYesThe interview question that was asked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this a read-only, non-destructive, closed-world call, so the safety profile is covered. The description adds genuinely new behavioral context by describing the shape of the result (a verdict from three named levels, what worked, the single fix, a stronger opener, presented as a feedback card) — valuable since there is no output schema.

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?

A single front-loaded sentence with no filler; the list of feedback components is dense but each item earns its place by describing the return. It is slightly run-on, but nothing is redundant.

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 simple three-parameter, read-only tool, the definition covers purpose and result shape, and the schema covers the inputs completely. The remaining gap is routing against the sibling mock-interview tool, which keeps it short of a 5.

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 100%, so all three parameters (role, question, answer) are already fully documented in the schema. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('Gives feedback on one practice interview answer') and even enumerates the feedback components, so the agent knows exactly what it gets back. It does not explicitly contrast itself with start_mock_interview, so sibling differentiation is left to inference from the phrase 'one ... answer'.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of an alternative such as start_mock_interview for a full interview. The only signal is the implicit scope of 'one practice interview answer', which the agent must interpret on its own.

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