Skip to main content
Glama

Product shot

product_shot

An ad photo of the uploaded product in a scene template (list_product_templates); brief adds copy or direction.

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": {
      "product_file": "<product_file>",
      "template_key": "<template_key>"
    },
    "name": "product_shot"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefNo
aspectNo1:1
num_imagesNo
product_fileYes
template_keyYes
confirm_creditsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations mark it as non-read-only and non-destructive, but the description adds nothing about the fact that this consumes credits (there is a `confirm_credits` parameter and an `estimate_cost` sibling) or that generation is likely asynchronous given `wait_for_generation`/`get_generation`. For a paid generation tool, that silence is a meaningful 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 short clauses, front-loaded with the core outcome and the template dependency; nothing is padded or redundant. It is compact to the point of under-specification, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, zero schema coverage, and an output schema that covers returns, the description should at minimum cover credit cost and the aspect/image-count controls. It omits both, so an agent cannot call this correctly without guessing at the remaining parameters.

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%, so the description must compensate, but it only touches `brief` (copy/direction) and obliquely `template_key`. It says nothing about `aspect`, `num_images`, `product_file`, or the meaning/units of `confirm_credits`, leaving four of six parameters unexplained anywhere.

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 concrete output (an ad photo of the uploaded product in a scene template), which clearly separates it from siblings like headshot, try_on, or text_to_speech. It is written as a noun phrase rather than a verb, so the generative action is implied rather than stated, costing it the top mark.

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?

It usefully points to `list_product_templates` as the source of the required `template_key`, which is real prerequisite guidance. However, it gives no when-to-use vs. when-not guidance and does not distinguish this from other image-generation siblings (headshot, try_on, generate), leaving that inference to the agent.

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