Skip to main content
Glama

set_contact_archived

Destructive

Archive or restore a contact using the current contact revision.

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>",
      "revision": "<revision>",
      "requestId": "<requestId>",
      "archived": "<archived>"
    },
    "name": "set_contact_archived"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
archivedYes
revisionYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds the notion that the write is revision-guarded, but never says what happens on a revision mismatch, whether archived contacts disappear from listings, or that the operation is reversible via the same tool.

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, but the brevity comes at the cost of needed detail rather than being optimally tight.

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 a destructive, non-idempotent mutation with four required undocumented parameters, no output schema, and concurrency semantics, the description leaves too much unstated — notably the role of requestId and the failure modes around revision conflicts.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four required parameters, so the description must carry that burden. It only hints that the revision must be 'current'; it says nothing about the contact id, why a UUID requestId is required, or that the boolean archived flag is what selects archive versus restore.

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 pair and resource ('Archive or restore a contact'), which clearly separates it from siblings that mutate contact attributes like update_contact_profile or set_contact_type. It stops short of naming any alternative, so there is no explicit sibling differentiation.

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 guidance on when to archive versus restore versus delete a contact, no prerequisites (e.g., how to obtain or refresh the revision), and no mention of what to do when the revision is stale. The agent must infer the whole usage context.

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