Skip to main content
Glama

Coupons

list_coupons
Read-onlyIdempotent

Coupons for buying packs: automatic ones and ones with a code, with who and which packs they are for, dates and how often they were used. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>"
    },
    "name": "list_coupons"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the call is scoped to a single venue and requires that venue's address and access key, which is meaningful behavioral context. It says nothing about ordering, volume, or pagination of the returned list, which is the main remaining gap.

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 sentences, front-loaded with what the tool returns, then the venue scoping constraint. Dense but every clause carries information; the comma-spliced enumeration of returned fields is slightly awkward but not wasteful.

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?

There is no output schema, so the description must convey return content, and it does: coupon type, audience, applicable packs, dates, and usage frequency. Combined with annotations covering the read-only profile, an agent has enough to call this correctly; only list ordering/size conventions are unstated.

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?

Schema description coverage is 100%, with both address and access_key documented in the schema itself, including the 'name in name.bookare.app' clarification. The description only restates that the venue is identified by address and access key, adding no format or syntax detail beyond the schema. 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 names the resource (coupons) and specifies the two kinds it returns (automatic and code-based) plus the attributes carried (audience, packs, dates, usage counts). The verb is implicit in the noun phrase 'Coupons for buying packs' rather than stated as 'list', but the scope is clear enough to distinguish it from create_coupon.

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?

Usage is only implied: it is a read of existing coupons, so an agent can infer it should be called before/alongside create_coupon rather than instead of it. There is no explicit when-to-use, when-not-to-use, or named alternative. The 'acts on one venue' clause gives scoping but not selection guidance.

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