Skip to main content
Glama

Create a preview ($1)

create_preview

Start a paid preview ($1): three logo directions with QA. Returns a preview_id and a status_url to poll. 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": {
      "brief": "<brief>"
    },
    "name": "create_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYes

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?

Adds real context beyond annotations: a $1 charge, an API key requirement, and an asynchronous workflow where you receive a preview_id and status_url to poll. The polling contract is genuinely useful. It does not spell out that with idempotentHint=false each repeated call incurs another charge, which would have earned a 5.

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, no filler, with the cost and deliverable front-loaded ahead of the return values and auth note. Every sentence carries distinct information.

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?

Given no output schema, the description covers what matters for invocation: price, auth prerequisite, return shape, and follow-up action. The only gap is the structure of the brief payload, which the nested schema partially covers but not fully.

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?

The description says nothing about the single 'brief' parameter or its nested fields, and top-level schema coverage is 0% (only name/style/trade carry inline descriptions). For a nested object with seven optional/required subfields, the description should at least name what a brief must contain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Start a paid preview') plus the deliverable ('three logo directions with QA'), which is enough to separate it from get_preview and create_pack. The cost marker ($1) further disambiguates it as the kickoff call rather than a retrieval.

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?

Implies the decision factors (it costs $1, it needs an API key) but never states when to choose this over create_pack or when not to start a new preview. An agent must infer the routing rule from the price tag alone.

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