Skip to main content
Glama

Record Unknown

record_unknown

Record a deterministic residual unknown with immutable mutation evidence, validating all evidence and relationship references and rejecting duplicate stable identities.

Instructions

Create one deterministic residual unknown and immutable mutation evidence. Validates all evidence and relationship references, and rejects duplicate stable identity.

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": {
      "domain": "protocol",
      "question": "Does this branch require an unavailable external service?",
      "severity": "medium",
      "relationships": [],
      "recommended_probes": [
        {
          "operation": "capture_process_scenario",
          "rationale": "Replay branch."
        }
      ],
      "required_authority": "controlled-replay",
      "required_confidence": "observed",
      "required_environment": null,
      "supporting_evidence_ids": [],
      "contradicting_evidence_ids": []
    },
    "name": "record_unknown"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
questionYesConcrete unresolved question to retain for later investigation.
severityYes
relationshipsYes
recommended_probesYes
required_authorityYes
required_confidenceYes
required_environmentYes
supporting_evidence_idsNoOrdered Evidence identifiers for the supporting observations.
contradicting_evidence_idsNoOrdered Evidence identifiers for the contradicting observations.
comparison_conclusion_scopeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds real value beyond them: validation of evidence and relationship references (i.e. calls can fail on dangling IDs) and duplicate-identity rejection, which explains the idempotentHint=false. It does not say what is persisted or returned, so it is useful but not rich.

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?

Two tight sentences with the verb and core guarantee front-loaded and no filler. Brevity is appropriate; the issue is under-specification rather than verbosity.

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 11-parameter, 8-required mutation tool with low schema coverage and no output schema, the description leaves most of the contract unexplained. It never states what identifier is returned, whether the creation is reversible, or what the domain/severity/authority fields actually mean to an agent composing a valid record.

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 27% across 11 params, so the description must compensate and largely does not. The clause about validating 'evidence and relationship references' gives partial meaning to supporting_evidence_ids, contradicting_evidence_ids and relationships, but severity, domain, required_authority, required_confidence, required_environment, recommended_probes and comparison_conclusion_scope get no explanation at all.

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 ('Create one deterministic residual unknown') plus the mutation-evidence side effect, which is enough to distinguish it from update_unknown and verify_unknown_resolution. It does not name those siblings explicitly, so it stops short of full 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 when-to-use guidance: no statement of when an unknown should be recorded versus updated (update_unknown) or verified (verify_unknown_resolution). The only conditional implied is 'rejects duplicate stable identity', which is a behavior, not a routing rule.

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