Skip to main content
Glama
Sign In

SAAX Protocol

by io.github.bryantrudy24
OverviewDiscussionsAdmin

Get supplier details

get_supplier_details

Returns the detailed record for one supplier in the SAAX Router index: identifier, name, description, services (name/endpoint/version), owner and source provenance. Call this after route_request or list_capabilities to inspect a specific supplier before preparing a commitment. Read-only; exact supplier_id match only (no enumeration). A registry entry is not a guarantee of service quality or 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": {
      "supplier_id": "<supplier_id>"
    },
    "name": "get_supplier_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
supplier_idYesThe supplier identifier (agent_id from list_capabilities/route_request results, or its decimal string form)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose read-only behavior, exact-match-only lookup, and a caveat that a registry entry is not a guarantee of service quality or verification. What it omits is failure behavior, e.g. what happens with an unknown supplier_id or whether results can be stale.

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 field enumeration and workflow guidance are front-loaded and no sentence is filler, but the opening sentence packs a long parenthetical list that is denser than needed. Overall it stays within a compact paragraph without restating the title.

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

Completeness5/5

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

For a single-parameter read tool with no output schema, the description covers what is returned, when to call it, what it will not do, and a trust caveat. An agent has everything needed to select and invoke it correctly.

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?

Schema coverage is 100% and the schema already explains the supplier_id format (agent_id or decimal string form), so baseline is 3. The description adds the exact-match-only constraint, which is genuine semantics beyond the schema's type and format notes.

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 names a specific verb and resource ("Returns the detailed record for one supplier") and enumerates the returned fields (identifier, name, description, services, owner, provenance). It is clearly distinguished from sibling enumerators like list_capabilities by the explicit "one supplier" and "no enumeration" framing.

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

Usage Guidelines5/5

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

It gives explicit sequencing guidance — call after route_request or list_capabilities, before preparing a commitment — which ties the tool to concrete workflow steps in sibling tools. It also states the exclusion (exact supplier_id match only, no enumeration), routing enumeration to other tools.

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