Skip to main content
Glama

AceRound AI Interview Copilot

learn_answer_style

Learn the user's own answer style from one interview record and return a style instruction that can be used as the extra answer requirement when starting an interview. Interview ids come from list_answer_style_sources. (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": {
      "interviewId": "<interviewId>"
    },
    "name": "learn_answer_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYesInterview id from list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false (a write) with destructiveHint=false, and the description usefully adds that sign-in with the interviews:write scope is required and that the call returns a style instruction. However, it never says whether the learned style is persisted as a profile — the presence of delete_learned_profile_answer and edit_learned_profile_answer siblings suggests it is, and that side effect is undisclosed.

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 with the action and its output, followed by the input source and the auth parenthetical; no filler sentences. It is slightly dense — three ideas packed into one sentence plus a parenthetical — but nothing is wasted.

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 one-parameter tool with full schema coverage and no output schema, the description covers what it does, where the input comes from, what it returns, and the auth scope needed. The remaining gap is whether the result is stored server-side and how large or representative the source record must be.

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?

With 100% schema coverage, the schema already documents the single interviewId parameter, so baseline is 3. The description adds 'from one interview record' (single, not batch), but it also conflicts with the schema: the description says ids come from list_answer_style_sources while the schema says 'Interview id from list_interviews', which could send an agent to the wrong source.

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?

States a specific verb ('Learn') and resource ('the user's own answer style'), plus the derived output ('a style instruction ... used as the extra answer requirement'). It also points to the sibling that supplies valid inputs, so an agent can place it precisely in a workflow without opening any 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?

The context is clear: this is a pre-interview step, run on a single interview record whose id comes from list_answer_style_sources, and its output feeds 'starting an interview'. No explicit exclusions or failure conditions are stated (e.g., what happens if the record is too short to learn from), keeping it below a 5.

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