Skip to main content
Glama
Sign In

SAAX Protocol

by io.github.bryantrudy24
OverviewDiscussionsAdmin

Validate an authority proof

get_authority_validation

Validates an authority proof against a commitment. Requires an active SAAX Premium subscription. For evidence verification, use get_evidence_verification.

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>",
      "proof": "<proof>",
      "commitment": "<commitment>"
    },
    "name": "get_authority_validation"
  }
}

Input Schema

NameRequiredDescriptionDefault
proofYesThe AuthorityProof object (proofType, issuer, subject, scope, validFrom, validUntil, signature, verificationScheme, verificationMaterial)
commitmentYesThe commitment or requested action the proof must authorize
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 exist, so the description carries the full burden. It usefully discloses a hard precondition (active SAAX Premium subscription), but says nothing about what happens on an invalid/expired proof, whether the call is read-only or mutating, or whether results are cached — significant gaps for a validation tool.

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, zero filler, with the core action front-loaded and the routing hint and precondition following in priority order. Nothing is repeated from the schema or title.

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?

With no annotations and no output schema, the description should at least hint at the validation result shape (valid/invalid, failure reason) and whether the operation has side effects. It covers the input-side precondition but leaves the entire result side unexplained.

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% and the schema already enumerates the AuthorityProof fields, so the baseline of 3 applies. The description adds no syntax, format, or value guidance beyond restating the proof/commitment pairing.

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 (validates) plus both operands (an authority proof against a commitment), which is precise enough that an agent can distinguish it from every sibling. It also explicitly separates itself from get_evidence_verification, the closest-sounding sibling.

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?

Names the alternative tool (get_evidence_verification) and the condition that selects it (evidence verification), and states the subscription prerequisite. It stops short of describing its own trigger conditions or any negative cases beyond the one alternative.

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