Skip to main content
Glama

Update Unknown

update_unknown

Append an immutable full-state revision and mutation evidence for a residual unknown; expected_revision blocks stale concurrent writers from overwriting newer analysis.

Instructions

Append one immutable full-state revision and mutation evidence. Requires exact expected_revision; stale concurrent writers fail instead of overwriting newer analysis.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status": "investigating",
      "severity": "medium",
      "resolution": null,
      "unknown_id": "unk_0000000000000000000000000000000000000000000000000000000000000000",
      "relationships": [],
      "expected_revision": 1,
      "recommended_probes": [],
      "required_authority": "controlled-replay",
      "required_confidence": "observed",
      "required_environment": null,
      "supporting_evidence_ids": [],
      "contradicting_evidence_ids": []
    },
    "name": "update_unknown"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesCurrent lifecycle or verification status.
severityYes
resolutionYes
unknown_idYesExact residual-unknown identifier.
relationshipsYes
expected_revisionYesExpected revision used to reject stale or mismatched input.
recommended_probesYes
required_authorityYes
required_confidenceYes
required_environmentYes
supporting_evidence_idsYesOrdered Evidence identifiers for the supporting observations.
contradicting_evidence_idsYesOrdered Evidence identifiers for the contradicting observations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description goes further by disclosing that revisions are immutable appends rather than in-place overwrites, and that concurrency is enforced optimistically via expected_revision, which is exactly the context needed to reconcile non-destructive-but-non-idempotent behavior.

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 tightly written sentences with the core operation first and the concurrency constraint second. No filler, nothing redundant with the tool name.

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?

For a 12-parameter full-state mutation with no output schema, the description covers the concurrency contract but not the full-replace semantics (that every required field is written, including empty evidence arrays) or what a successful call returns. Adequate orientation, but an agent would still guess at several important behaviors.

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 only 42% across 12 required parameters, so the description must compensate, and it does not. It explains only expected_revision; status, severity, resolution, evidence ID arrays, required_authority/confidence/environment, recommended_probes, and relationships are left entirely to the schema.

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: 'Append one immutable full-state revision and mutation evidence' for an unknown record. Clear enough to differentiate from a plain record/verify operation, though it never names the sibling tools (record_unknown, verify_unknown_resolution) it complements.

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?

Provides a concrete precondition — requires exact expected_revision and stale concurrent writers fail — which tells the agent when a call will be rejected. It does not say when to prefer this over record_unknown or verify_unknown_resolution, nor when not to use it, 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.

Deploy Server

Other Tools