Skip to main content
Glama

Get a Tested receipt

get_setup_receipt
Read-onlyIdempotent

The proof behind a Tested setup: how it was tested, what went wrong, and the link to the receipt on the setup page. A setup that is only Researched says it has not been run yet.

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": {
      "slug": "<slug>"
    },
    "name": "get_setup_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe setup slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered. The description adds genuine behavioral context by describing the returned payload (test narrative, failures, receipt link) and by noting what a non-Tested setup reports, though it does not say whether an untested slug returns an empty/negative result or an error.

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?

Two short sentences, front-loaded with what the tool exposes, followed by the state clarification. The phrasing 'The proof behind a Tested setup' is slightly metaphorical but earns its place by framing the payload; nothing is redundant.

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 simple single-parameter read with no output schema, the description should carry the return-shape burden and it partly does by listing the receipt contents. It leaves open the failure mode for untested or unknown slugs and does not mention the link's target format, which a complete definition would resolve.

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?

There is a single required parameter and the schema documents it at 100% coverage ('The setup slug.'). The description adds no further meaning about slug format, where to obtain it, or what happens with an unknown slug, so the baseline of 3 applies.

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

Purpose4/5

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

The description identifies a specific resource (the receipt for a Tested setup) and enumerates its contents: how it was tested, what went wrong, and the link on the setup page. It is clear what the tool returns, but it never explicitly contrasts itself with the closely named sibling get_setup or with search_setups, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no explicit statement of when to call this rather than get_setup, find_tested_setups, or search_setups. The only usage-adjacent hint is the remark that a setup which is merely Researched has not been run yet, which implies the tool is for Tested setups but does not route the agent between alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources