Skip to main content
Glama
rupturetrace-mcp

rupturetrace-mcp

by Susan571

describe_protocol

Returns the RuptureTrace protocol: rubric, 12 audited relations, allowed statuses, per-round JSON schema, model instructions, and fixed scoring policy for relation-guided claim assessment.

Instructions

Return the RuptureTrace protocol: rubric, the 12 audited relations, allowed statuses, the per-round JSON output schema, model instructions and the fixed scoring policy.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does convey that the return is a fixed, canonical specification ("fixed scoring policy"), which implies determinism and no side effects, but it never states that the call is read-only, parameterless, idempotent, or how large the returned payload is.

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?

A single front-loaded sentence with the verb and resource first, followed by the content list. The list is long but each item earns its place by telling the agent what the payload contains; no filler or repetition.

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 parameters and no output schema, the description must describe the return value itself, and it does so by enumerating the protocol components. The only gap is the absence of guidance on when in the workflow to call it, which is a usage concern rather than a completeness one.

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?

The tool takes zero parameters, so the baseline is 4. Nothing in the description misrepresents the argument surface, and there is no parameter semantics to add.

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 pairs a specific verb ("Return") with a specific resource ("the RuptureTrace protocol") and enumerates the payload contents — rubric, 12 audited relations, allowed statuses, per-round JSON output schema, model instructions, fixed scoring policy. That enumeration effectively separates it from the sibling assessment tools (assess_claim, evaluate_run, etc.), though no sibling is named directly.

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?

There is no explicit when-to-use sentence and no alternative is named. Usage is only implied: an agent can infer this is the spec-fetch step that precedes the assess/evaluate/submit tools, but the description never states that ordering or any precondition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.