Skip to main content
Glama

Quote a Playground image generation

playground_image_quote
Read-onlyIdempotent

Read the current credit cost for one image and up to three image references. Does not submit a job. Returns model pricing and the quoted image settings.

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": {
      "projectId": "<projectId>",
      "modelId": "<modelId>"
    },
    "name": "playground_image_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelIdYesCanonical model ID returned by model discovery or resolution; preserve the user’s selected model.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
aspectRatioNoOutput width-to-height ratio supported by the selected model, such as 1:1 or 9:16.
inputImageCountNoNumber of reference images that will be supplied to the image model for this quote.

Output Schema

NameRequiredDescriptionDefault
creditsYes
modelIdYes
modelNameYes
aspectRatioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 the safety profile is covered. The description adds the useful clarification that no job is submitted and that model pricing plus quoted settings come back, but it says nothing about pricing volatility, auth/credit requirements, or error behavior for unsupported models.

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 the core action front-loaded, followed by the negative scope constraint and the return payload. No filler or redundancy.

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 an output schema present, return values need not be explained, and the description still briefly summarizes them. Annotations carry the safety profile and the schema carries parameter detail, leaving only the missing explicit alternative-routing as a gap.

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%, so all four parameters are already documented in the schema. The description only echoes the 'up to three image references' bound, which the schema already enforces with maximum: 3, so it adds little semantic meaning beyond the structured fields.

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 verb and resource: read the current credit cost for one image plus up to three reference images. It distinguishes itself from job-submitting siblings via 'Does not submit a job', though it never names the sibling that does (e.g. playground_generation_confirm), so the differentiation is implied rather than explicit.

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?

The line 'Does not submit a job' implies this is a pre-flight pricing check to run before a generation confirm, but the description never states when to use it versus alternatives or what prerequisite state is required. Usage is inferable but not spelled out.

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.