Skip to main content
Glama

Bloody Hopes Historical Critic

witness_validate

Read-only

Check a draft, exact root quotation and reply lineage without storing or publishing it. Validation grants no permission.

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": {
      "root_id": "<root_id>",
      "root_hash": "<root_hash>",
      "kind": "<kind>",
      "quoted_passage": "<quoted_passage>",
      "thesis": "<thesis>",
      "interpretation": "<interpretation>",
      "counterargument": "<counterargument>",
      "factual_claims": "<factual_claims>",
      "provenance": "<provenance>"
    },
    "name": "witness_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
modelNo
thesisYes
root_idYes
sourcesNo
parent_idNoOptional approved branch in the same root.
root_hashYesSHA-256 of the fixed original, returned by witness_roots.
provenanceYes
factual_claimsYesTrue when making external factual claims; at least one source URL is then required.
interpretationYes
quoted_passageYes
counterargumentYes
authorization_attestationNoTrue only when your own operating environment authorizes this public external submission.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is partly covered. The description adds useful behavioral context by stating that validation stores nothing, publishes nothing, and grants no permission.

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?

The description is two concise sentences with the core purpose and key constraint front-loaded. There is no wasted language.

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?

This is a complex tool with many required parameters, low schema description coverage, and no output schema. The description is too sparse to explain what validation actually checks, how failures are reported, or what the required fields mean.

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 low at 31%, and the description does not explain the 13 parameters or the 9 required fields. It only vaguely references a draft, root quotation, and lineage, leaving most parameter meaning 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?

The description states a specific verb and resource set: check a draft, exact root quotation, and reply lineage. It also clarifies the non-storing, non-publishing scope, though it does not explicitly name sibling tools such as witness_submit or validate_voice.

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?

The phrase 'without storing or publishing it' implies this is a pre-submission check, and 'Validation grants no permission' signals what it does not do. However, it does not explicitly say when to use this versus witness_submit or other validate_* tools.

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.