Skip to main content
Glama

Affine Earth Math Court Remote

vqbit_jetstream_verify

Read-onlyIdempotent

Affine.Earth Sovereign vQbit & NATS JetStream Fact Verifier: verifies lexical and domain claims against PROT_READ mmap facts.m8.idx (< 35 flicks) and live NATS JetStream (GAIA_FACT_BUCKET, GAIA_SPATIAL_BOND_ARCHIVE, KV_gaia_s4_lexicon, GAIAFTCL_LANGUAGE_GAME), with optional verified chi=+1 closure seal write-back.

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": "vqbit_jetstream_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
stemNoConcept stem or claim key, e.g. book
domainNoOptional domain name when verifying non-lexical facts
target_langNoISO language tag for lexical bond verification, e.g. es
seal_closureNoWhen true and chi == +1, publish verified closure to JetStream
candidate_wordNoCandidate target word or canonical claim value, e.g. libro

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

C2.2/5.0
Behavior1/5

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

The description states an 'optional verified chi=+1 closure seal write-back' that publishes to JetStream when seal_closure is true, which is a state-modifying operation. Annotations declare readOnlyHint=true and destructiveHint=false, directly conflicting with that advertised write path; the description also adds no auth, latency, or side-effect detail beyond listing bucket names.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One run-on sentence stacks system names, an mmap index path, a timing claim, four bucket identifiers, and a closure-seal clause without a leading plain-language statement of what the tool does. Nearly every clause needs external documentation to interpret, so it is dense rather than concise.

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?

With five optional parameters, no output schema, and a verification result presumably expressed as chi or a verdict code, the description never explains what a call returns or how to read the result. For a tool whose output semantics are non-obvious, omitting return-value explanation leaves a real gap.

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

Parameters3/5

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

Schema description coverage is 100%, so all five parameters are already documented in the schema, establishing a baseline of 3. The description adds only bucket names and the chi=+1 precondition for seal_closure, with no explanation of how stem, domain, target_lang, and candidate_word interact to form a query.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does name a specific verb and resource ('verifies lexical and domain claims') and its two backing stores, so the general function is inferable. But it is buried under proprietary jargon ('vQbit', 'PROT_READ mmap facts.m8.idx (< 35 flicks)', 'chi=+1 closure seal') that an agent cannot decode, and nothing distinguishes it from the many sibling verify_* tools (verify_topological_word, verify_presented_pair, verify_jordan_bond), which plausibly also handle 'bonds' and 'words'.

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?

No sentence says when to choose this tool over the sibling verifiers, nor when not to. The only routing signal is implicit in the schema parameter descriptions ('domain' for non-lexical facts, 'target_lang' for lexical bond verification), which is schema content, not description guidance.

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