Skip to main content
Glama
Sign In
TruthGate

TruthGate

by ay7627514-dotcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

truthgate_verify

Verify final candidate outputs against evidence and tool traces to block unverified completions.

Instructions

Verify Hermes' final candidate against evidence and tool traces.

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": {
      "payload_json": "<payload_json>"
    },
    "name": "truthgate_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
payload_jsonYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2/5.0
Behavior1/5

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

No annotations provided. The description does not disclose side effects, permissions, or behavior (e.g., read-only, destructive). For a verification tool, it should indicate if it modifies state or requires specific access.

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

Conciseness3/5

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

The description is a single sentence with minimal noise, but it is too brief and lacks structure. Some detail could be added without sacrificing conciseness.

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?

Given a single parameter, no output schema details provided, and no annotations, the description fails to explain what the output represents or error handling. The tool's completeness is insufficient for a verification task.

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

Parameters1/5

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

The sole parameter 'payload_json' has no description in the schema (0% coverage). The tool description does not explain what the payload should contain or its role in verification.

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 states the tool verifies 'Hermes' final candidate' against evidence and tool traces, indicating a specific verb and resource. However, 'Hermes' and 'candidate' are domain-specific terms not explained, reducing clarity. It distinguishes from siblings by implying a final verification step, but not explicitly.

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 guidance on when to use this tool versus siblings (truthgate_preflight, truthgate_authorize). The description does not provide context for appropriate usage or alternatives.

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