Skip to main content
Glama
Sign In

SAAX Protocol

by io.github.bryantrudy24
OverviewDiscussionsAdmin

Verify evidence against acceptance criteria

get_evidence_verification

Verifies external evidence against a commitment's acceptance criteria. Requires an active SAAX Premium subscription. For authority proof validation, use get_authority_validation.

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": {
      "subscriptionEmail": "<subscriptionEmail>",
      "evidence": "<evidence>",
      "commitment": "<commitment>",
      "criterion": "<criterion>"
    },
    "name": "get_evidence_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
evidenceYesThe evidence object (evidenceId, evidenceType, issuer, subject, payload, payloadHash, signature, verificationScheme, commitmentId, acceptanceCriterionId, ...)
criterionYesThe verification policy / acceptance criterion
commitmentYesThe commitment object the evidence binds to
subscriptionEmailYesThe subscription email (must have an active SAAX Premium subscription)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses an authorization prerequisite (SAAX Premium subscription), but says nothing about whether verification mutates state, what a failed verification yields, or how results are returned.

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?

Three short sentences, front-loaded with the core purpose, then prerequisite, then sibling routing. Every sentence earns its place with zero filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-required-parameter verification tool with no output schema and no annotations, the description covers purpose, prerequisite, and sibling routing, but omits what the verification result contains or how success/failure is signaled, leaving a gap the agent must discover at call time.

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 four parameters (evidence, criterion, commitment, subscriptionEmail) are already documented in the schema. The description adds no format or interpretation detail beyond what the schema supplies, making the baseline 3 appropriate.

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?

States a specific verb (verifies) and resource (external evidence against a commitment's acceptance criteria), which is precise enough to distinguish it from the other commitment tools. It also names the closely related sibling get_authority_validation and the domain in which that one applies.

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?

Gives a clear conditional route to an alternative ("For authority proof validation, use get_authority_validation") plus a prerequisite (active SAAX Premium subscription). It does not describe the full when-not conditions or the relationship to tools like get_commitment_status, so it falls short of exhaustive 5-level guidance.

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

All SAAX Protocol 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