Skip to main content
Glama

Price a picture

picture_price
Read-only

Quotes what a picture costs here before it is planned or made, as Create quotes it: one picture, one of a real place or thing with the most the search for its real photographs may spend, and writing its prompt from this business's own receipts. Read it when the owner asks what a picture costs or when you plan pictures, and say the numbers; it spends nothing.

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": "picture_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new context beyond that: "it spends nothing," which tells the agent the quote incurs no monetary charge, and that the price is computed "as Create quotes it," implying consistency with the actual creation path. It stops short of saying whether a price expires or what the returned quote contains.

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?

Purpose is front-loaded and the whole definition is one sentence of roughly fifty words, so there is no padding by volume. However, the chain "one picture, one of a real place or thing with the most the search for its real photographs may spend" is a garden-path clause that costs the reader more than it returns.

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?

With one optional parameter, a closed-world read-only profile, and no output schema, the definition covers the essentials. It still leaves open what the quote actually returns (a number? a breakdown?) and how the quoted picture specifications are supplied, which matters for a tool that describes a rich picture concept but only accepts a project identifier.

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?

The single optional `project` parameter is fully documented in the schema (100% coverage), so the baseline is 3. The description says nothing about what the project argument means or what happens when it is omitted, adding no meaning beyond the schema.

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?

"Quotes what a picture costs here before it is planned or made" gives a specific verb (quote) and resource (picture price) with a clear precondition. The trailing clause about "one of a real place or thing... and writing its prompt from this business's own receipts" muddies the read with vague, unparseable modifiers rather than sharpening the distinction from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit triggers: "when the owner asks what a picture costs or when you plan pictures," plus an output instruction ("say the numbers"). No when-not guidance or named alternative is offered, but the use context is concrete enough to route correctly.

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.