Skip to main content
Glama

AceRound AI Interview Copilot

edit_learned_profile_answer

Change the value of a learned answer; later applications that ask the same question use the new value. Replies with the value as read back. (Requires the user's sign-in with scope job_applications: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": {
      "normalized": "<normalized>",
      "value": "<value>"
    },
    "name": "edit_learned_profile_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
normalizedYesNormalized key of the learned answer, copied from get_job_apply_profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, non-destructive, closed-world write. The description goes beyond them by disclosing the propagation behavior (future applications reuse the new value), the response shape (echoes the value as read back), and the required auth scope job_applications:write. It does not say what happens if the normalized key does not exist, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences plus a parenthetical auth note, with the primary effect front-loaded before the side effects. Every clause carries information an agent needs; nothing is filler or redundant with the title.

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 two-parameter mutation with no output schema, the description covers the effect, the persistence consequence, the return echo, and the permission requirement. The remaining gap is error behavior for an unknown or stale 'normalized' key, which matters for a keyed update but is not addressed.

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 coverage is 50%: 'normalized' is documented in the schema as the key copied from get_job_apply_profile, while 'value' carries no schema description. The description confirms that the value is the replacement content and that it is read back, but adds no format, validation, or lookup semantics beyond that. Baseline 3 is appropriate given the schema does half the work.

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 ("Change the value of a learned answer") and adds the downstream effect that future applications asking the same question will use the new value. That distinguishes it from the delete_learned_profile_answer sibling without naming it. It stops short of explicitly contrasting with update_job_apply_profile, so not a 5.

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?

The use case is implied: correct an already-learned answer when its stored value is wrong, since later applications inherit it. There is no explicit when-not guidance (e.g., use update_job_apply_profile for other fields, or delete_learned_profile_answer to remove it entirely). The agent must infer the boundary from sibling 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.

Resources