Skip to main content
Glama

Trueprice

Checked promo codes

store_codes
Read-onlyIdempotent

Promo codes for a store that Trueprice applied in a real cart and the store accepted.

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": {
      "domain": "<domain>"
    },
    "name": "store_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesStore domain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes real behavioral context by explaining that codes are validated through a real cart and store acceptance, implying a curated non-exhaustive set. It does not disclose whether results are cached, how fresh they are, or what expiry information accompanies each code, so it goes somewhat beyond but not substantially beyond the annotations.

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?

A single tight sentence with no filler; the verification qualifier is placed where it reads first. Minor deduction because it is a noun phrase rather than leading with an action verb.

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 one-parameter read-only tool with rich annotations and no output schema, the description covers what the tool returns conceptually. However, it never indicates the shape or fields of the result (code, discount, expiry, last-checked), leaving the agent to discover the response structure at call time.

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?

Only one parameter (domain) exists and schema description coverage is 100%, with the schema already giving an example. The description's phrase 'for a store' merely restates what the schema documents, so baseline 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 the specific resource (promo codes for a store) and adds a meaningful qualifier: these are codes verified by an actual cart application and store acceptance, which distinguishes it from a generic promo-code list. It lacks an explicit verb like 'list' or 'get', but the retrieval intent is unambiguous given the domain parameter.

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 guidance on when to use this tool versus siblings such as cheapest_path or lookup_price, nor any stated prerequisites or exclusions. The agent must infer from the name alone that this is the promo-code lookup for a given store domain.

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