Skip to main content
Glama

AceRound AI Interview Copilot

update_job_intent

Update the user's job preferences: each dimension passed replaces the old value (pass the full new array to append); others stay. Replies with the preferences 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": {
      "patch": "<patch>"
    },
    "name": "update_job_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYes
markInterviewedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, and the description adds real context beyond them: the required job_applications:write scope, the fact that omitted dimensions are preserved, and that the response echoes the preferences as read back (valuable given there is no output schema). It does not cover failure modes, but the safety profile is well served.

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?

Three compact clauses, front-loaded with the action, then the merge rule, then the return behavior, with auth as a trailing parenthetical. No sentence is redundant and the ordering matches what an agent needs to decide and then call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return behavior and auth are covered, which compensates for the absent output schema, and the nested patch object's core rule is stated. What remains missing is the meaning of markInterviewed, a boolean side-effect flag whose purpose an agent cannot infer from a 0%-coverage schema.

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 0%, so the description must carry parameter meaning. It explains the patch object's replace/append semantics well, but never mentions markInterviewed or the individual dimension fields, leaving one of two top-level parameters entirely unaddressed by prose.

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?

"Update the user's job preferences" gives a specific verb and resource, and the replace-vs-keep clause defines the update model precisely. It does not explicitly contrast with the read-side sibling get_job_intent, but the write verb and scoped resource make the distinction inferable.

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 description implies usage through its patch semantics ("each dimension passed replaces the old value... others stay"), which tells an agent how to call it incrementally. However, it never states when to prefer this tool over siblings, nor any precondition beyond the auth scope, so guidance is implied rather than explicit.

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