Skip to main content
Glama

Live offers

list_offers
Read-onlyIdempotent

The business’s offers running now, with their end dates and terms. This is the complete list of its current offers.

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": {
      "business": "<business>"
    },
    "name": "list_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessYesThe business id from find_businesses, e.g. "carat-story".

Output Schema

NameRequiredDescriptionDefault
offersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 safety is covered. The description adds two real behavioral facts beyond that: results are filtered to currently active offers, and the response is a complete list rather than a paginated or partial one. An output schema exists, so return-shape detail is not required here.

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 with the scope stated first. The second sentence is partly redundant with the first, though 'complete' does add the non-pagination signal; trimming the repetition would make it tighter.

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

Completeness4/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 rich annotations and an output schema, the description supplies the key semantic distinction (only current offers) and the completeness guarantee. Nothing an agent needs in order to call this correctly is missing, though a note on ordering or an empty-result meaning would fully close it out.

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 parameter and the schema documents it fully (pattern, length, example, and a pointer to find_businesses for obtaining the id). The description adds nothing about the business argument, so this is the baseline case where the schema does all the work.

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 names a specific resource (the business's offers) and a precise scope (those running now), plus what each entry carries (end dates and terms). It does not explicitly contrast itself with siblings such as list_collections, but the resource is distinctive enough that an agent can identify it from the name plus this text.

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?

The phrase 'running now' effectively defines the condition under which this tool returns data, implying expired or future offers are excluded. There is no explicit 'use X instead' routing, but within this catalog there is no obvious competing offers-listing tool, so the guidance is adequate without being exhaustive.

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