Skip to main content
Glama
Sign In

HiveAttest

by io.github.srotzin
OverviewDiscussionsAdmin

attest_cargo_validate

Validate a payload against a registered cargo type schema (C17). Reference-grade implementation. Wire format normative; production-grade is Layer B.

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": {
      "cargo_type_id": "<cargo_type_id>",
      "version": "<version>",
      "payload": "<payload>"
    },
    "name": "attest_cargo_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesPayload to validate against the schema
versionYesCargo type version
cargo_type_idYesRegistered cargo type ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool is reference-grade and wire-format normative, which is useful context. However, it does not mention return values, error behavior, or side effects, leaving important behavioral gaps.

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?

Two concise sentences: the first front-loads the core purpose, and the second adds a necessary qualification about reference-grade use. No filler or redundancy.

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?

The tool has no output schema and no annotations, so the description must explain return values and behavior. It does not specify what a validation result looks like or how errors are reported, making the description incomplete for a tool with no structured output.

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?

The input schema has 100% description coverage for all three parameters (cargo_type_id, version, payload), so the baseline is 3. The description adds no parameter-specific details beyond what the schema already provides.

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

Purpose5/5

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

The description states a specific action ('Validate') on a specific resource ('payload against a registered cargo type schema') and includes the identifier 'C17'. This clearly differentiates it from sibling tools like register, snapshot, and verify.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear usage boundary: 'Reference-grade implementation. Wire format normative; production-grade is Layer B.' This tells the agent to use it for reference/wire-format conformance and not for production, while implying an alternative. It does not name sibling tools but offers explicit when-to-use guidance.

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

All HiveAttest toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources