Skip to main content
Glama

List promo recipes

list_recipes
Read-only

The promo recipes, their scenes, their line-ups (fixed scene lists, each with what it requires and its 9:16 draft price in credits: a draft needs every slot of one) and what each slot needs, with an example still. Quick line-ups are marked with what each is made from (quick), and each recipe that has one names it in quick_lineup. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The readOnlyHint annotation already marks this as a safe read, so the bar is lower; the description still adds genuine context the annotation does not, namely that the call is free and how draft pricing works (a draft consumes every slot of one, priced in credits). It does not describe ordering, size, or whether the catalog can change between calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every clause carries real information and nothing is filler, but the whole thing is one long run-on sentence with stacked parentheticals ('(fixed scene lists, each with what it requires and its 9:16 draft price in credits: a draft needs every slot of one)') that make it hard to parse. It is also not front-loaded with the action, opening on a bare noun phrase instead of what the tool does.

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?

With no parameters and no output schema, the description carries the full burden of describing the return shape, and it does so thoroughly: scenes, line-ups, per-slot requirements, credits pricing, example stills, and the quick-lineup markup with quick_lineup naming. Only the overall list structure and size are left implicit.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not need to compensate for any schema gaps here.

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 clearly (promo recipes) and enumerates what comes back with it — scenes, line-ups, slot requirements, draft price, example still — so an agent knows what it will get. It never states an explicit verb ('list') and gives no sibling differentiation against list_formats, list_shorts, or get_promo, but the resource is unambiguous.

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 when-to-use guidance at all: nothing says whether to call this before make_promo, instead of get_promo, or how it relates to the other list_* tools. The single word 'Free' is the only hint about cost context, which is not usage 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