Skip to main content
Glama

update_application

Change a tracked job application's status or notes by ID to keep your job search records current.

Instructions

Update the status or notes of a tracked application

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": {
      "id": "<id>"
    },
    "name": "update_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesApplication ID from track_application
notesNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation tool. It does not say whether this is a partial merge (omitted fields left intact) or a replace, whether status transitions are validated, or what happens when the id is unknown or invalid.

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 or redundancy. Its brevity is efficient rather than padded, though the same brevity contributes to the specification gaps scored elsewhere.

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

Completeness2/5

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

For an unannotated mutation tool with no output schema and two of three parameters undocumented in the schema, the definition is too thin. It should state the merge semantics, the success/failure response, and the tracking prerequisite to be callable with confidence.

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 only 33% — just the id field is documented — so the description must compensate. It does partially by naming status and notes and, via 'or', implying either can be updated independently, but it adds nothing about notes replacing existing text or about which status values are legal (left to the schema enum).

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 (update) plus the resource (a tracked application) and the two updatable fields (status, notes). An agent can tell this apart from track_application (which creates) and list_applications, though the description never names a sibling explicitly.

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 guidance. It never states the prerequisite that the application must already be tracked, nor points to track_application for creating new ones, so the agent must infer the boundary between tracking and updating.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.