Skip to main content
Glama

Machine record for a report

machine_record
Read-onlyIdempotent

The unified machine record for one observation: subject, grade, findings (in full), capabilities with verification, and the evidence roots, manifest and verifier links that let anyone check it offline. Give id (report, d1:, f1: or manifest sha256) or domain for the latest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "machine_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it safe, idempotent, closed-world and non-destructive, so the bar is lower. The description adds real value beyond them by disclosing the shape of the payload (findings in full, capabilities with verification, evidence roots and verifier links so a third party can check offline), which tells the agent what it receives and why it is authoritative.

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 sentences, no filler: the first front-loads the resource and its contents, the second front-loads the invocation rule. The content list is dense but each item is informative; only the prefix enumeration could be tighter.

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?

With no output schema, the description takes on the job of describing returns and does so adequately by naming the major sections of the record. Combined with the annotation coverage, an agent has enough to call it correctly, with the id-prefix distinctions the main remaining ambiguity.

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 burden and largely does: it enumerates valid id forms (report, d1:, f1:, manifest sha256) and explains that domain yields the latest record. It still leaves the exact difference between the four id prefixes unexplained, so the agent must guess which prefix to use.

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?

Names a specific resource (the unified machine record for one observation) and enumerates what it contains: subject, grade, findings, capabilities with verification, evidence roots, manifest and verifier links. That is far more concrete than the title, though it never contrasts itself with siblings like explain_finding or list_verified_capabilities, which overlap in content.

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?

Gives the selection rule for the inputs — supply an id or a domain for the latest — which is genuine usage guidance for calling it. It does not say when a caller should prefer this tool over the sibling tools that expose findings or verified capabilities, so alternatives are left implicit.

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.