Skip to main content
Glama

TrueInterview

Update a contact

update_contact
Idempotent

Change one contact by its id: mark it saved, contacted (only after the candidate says they wrote to the person) or dismissed, or set a note. It records what the candidate did and reaches nobody.

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": {
      "contact_id": "<contact_id>"
    },
    "name": "update_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
statusNo
contact_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description reinforces the non-outreach nature ('reaches nobody') and adds the 'contacted' precondition, which is not in the annotations. It does not say whether unmentioned fields are left untouched or how status and note interact when both are supplied.

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 sentences, zero waste. The mutation scope and field list come first, followed by the behavioral clarification. Each sentence earns its place.

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?

A simple three-parameter mutation with no output schema and full annotation coverage; the description covers what changes, the key, and the outreach constraint. The remaining gap — partial-update semantics when only some fields are supplied — is minor but real.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 the load — and it does, naming all three parameters: contact_id as the lookup key, the three status values, and note as a settable field. It falls short of explaining whether note replaces prior text or whether status and note can be combined in one call.

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?

The description states a specific verb and resource ('Change one contact by its id') and enumerates the exact mutable fields: status values saved/contacted/dismissed and note. It is clear enough to distinguish a mutation from read siblings like list_contacts or find_contacts, though it 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 Guidelines3/5

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

There is one real usage constraint: 'contacted' only after the candidate says they wrote to the person. That is genuinely useful gating. However, there is no guidance on when to use this versus other update_* tools, and no statement of when not to use it.

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