Skip to main content
Glama

Lumen House

get_offer

Read-onlyIdempotent

Read exact published offer, price, availability, provenance and terms. Does not purchase or prove paid fulfillment.

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": {
      "id": "<id>"
    },
    "name": "get_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds real value by bounding scope negatively ("Does not purchase or prove paid fulfillment"), which prevents the agent from expecting transactional confirmation. It does not cover what happens for an unpublished or unknown id, nor whether price is a snapshot.

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?

Two sentences, front-loaded with the positive capability and immediately followed by the boundary. Every clause carries information; nothing is padded.

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 one-parameter read with full annotations, the description is close to sufficient and even previews returned fields in lieu of an output schema. The remaining gap is the identifier semantics and the failure mode for missing/unpublished offers, which the agent needs to call it reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required `id` parameter with 0% schema description coverage, and the description never mentions it or its role. The pattern constraint and the term "published" suggest a slug-like offer identifier, but the description does nothing to explain the mapping or validate format assumptions.

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?

"Read exact published offer" names a specific verb and resource and enumerates what comes back (price, availability, provenance, terms), so the purpose is unambiguous. It does not name or differentiate itself from search_offers, which is the sibling an agent is most likely to confuse it with.

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

Usage Guidelines3/5

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

The word "exact" plus the id-based schema implies this is the lookup-by-identifier path once a specific offer is known, with search_offers as the discovery path. That inference is never made explicit, and there is no statement of when-not to use it beyond the negative scope sentence.

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