Skip to main content
Glama

Buy the Production Pack ($19)

create_pack

Buy the Production Pack for a chosen direction ($19, less the preview credit). Returns an order_id and a status_url. Needs an API 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": {
      "preview_id": "<preview_id>",
      "concept_id": "<concept_id>"
    },
    "name": "create_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
concept_idYes
preview_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, and openWorld=false, so the safety profile is covered. The description adds genuinely new context beyond that: a concrete price with a credit offset, the auth requirement, and the returned fields (order_id, status_url). It misses the critical operational detail that repeating the call charges again despite the preview credit.

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?

Three short sentences with no filler, front-loading the action, price, return values, and auth requirement in order of importance. Nothing repeats the schema or annotations verbatim.

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 payment tool with no output schema the description does well to name the return fields and price, but it omits what happens on a duplicate call, whether the charge is refundable, and how the two identifiers are sourced. An agent could invoke it correctly but not safely.

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?

Schema description coverage is 0% for two required parameters, so the description must carry the full burden and does not. 'A chosen direction' loosely gestures at concept_id, but neither concept_id nor preview_id is explained, nor is where to obtain the preview_id that the pricing clause depends on.

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 states a specific verb and resource ('Buy the Production Pack') and scopes it to 'a chosen direction,' so an agent can distinguish it from create_preview or get_pack. It stops short of explicitly naming the sibling it must follow, leaving that relationship to be inferred from the preview-credit mention.

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 implied rather than stated: the 'less the preview credit' clause hints that a create_preview call should precede this one, and the API-key sentence flags a prerequisite. There is no explicit when-to-use, when-not-to-use, or 'do not call twice' guidance for a paid action.

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