Skip to main content
Glama
Sign In

RoboTrunk

by com.robotrunk
OverviewDiscussionsAdmin

Read RoboTrunk's trust manifest

get_trust_manifest
Read-onlyIdempotent

Returns RoboTrunk's trust manifest whole: what the service is, and that checkout at a listed store is real: the store is the seller, charges and ships, and RoboTrunk never sees the card. It also holds RoboTrunk's published statistics and, last, the contract of its one test demo checkout (no real charge, no order, no shipping). Use when you want to check what RoboTrunk claims about itself. It needs no arguments; its one optional field, shopping_session_id, is the correlation ID every tool accepts. Error recovery: rate_limited means wait 60 seconds; service_unavailable means retry later; network_error means call again; any other error, including tool_layer_failure: retry once, then call submit_feedback. Next: search_catalog to shop. Full guide: get_tool_guide or /agent/tools.json#get_trust_manifest Example call: {}

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

Input Schema

NameRequiredDescriptionDefault
shopping_session_idNoOptional server-issued shopping session correlation ID. It is not purchase authority.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description goes further by disclosing that no arguments are required, that the demo checkout involves no real charge, order, or shipping, and by giving an explicit error-recovery map (rate_limited → wait 60s, service_unavailable → retry later, network_error → call again, other → retry once then submit_feedback). This is exactly the added context annotations cannot carry.

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?

Front-loaded with what the manifest contains, then optional-parameter note, error recovery, and next step — a sensible order. It is a dense single paragraph with semicolon-chained clauses and some over-specification ('no real charge, no order, no shipping'), which keeps it out of the top band.

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 no-argument read tool with no output schema, the description fully covers what comes back (the manifest's four constituent parts), that no input is needed, failure handling, and the recommended follow-up call. An agent has everything required to invoke and interpret it.

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%, so the baseline is 3, but the description adds meaning by stating the tool 'needs no arguments' and that shopping_session_id is 'the correlation ID every tool accepts' — cross-tool scope that the schema does not convey. It does not restate the UUID pattern, which the schema already handles.

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 RoboTrunk's trust manifest whole') and then enumerates the manifest's contents: the service identity, the store-is-seller checkout guarantee, published statistics, and the demo checkout contract. No sibling tool in the list deals with trust claims, so it is cleanly distinguishable without opening the schema.

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?

'Use when you want to check what RoboTrunk claims about itself' gives a clear selection context, and 'Next: search_catalog to shop' routes the agent forward. It stops short of explicitly naming a when-not-to-use case or contrasting with a sibling, so it falls just below the top band.

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

All RoboTrunk 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