Skip to main content
Glama
Sign In

PopNow

by io.github.popnow-ai
OverviewDiscussionsAdmin

Create an image

create_image

Make a new picture from a description. Uses site credits with OAuth or USD with an API key; the tool quotes the price. Returns the picture and a link.

Input Schema

NameRequiredDescriptionDefault
modelNoOptional PopNow model id (see list_models). Leave empty for the default, Nano Banana 2.1.
promptYesWhat the picture should show, in plain words. Describe the subject, setting, style and mood.
max_usdNoAPI key only: maximum approved USD as a decimal string with up to 9 fractional digits. Set currency to USD. Only set after the user confirms the quoted cost_usd. Never convert max_credits.
currencyNoBilling unit: USD for API keys; credits for OAuth (optional for existing OAuth clients).
max_creditsNoOAuth only: the most site credits the user agreed to spend on this. Only set it after the user confirmed a quoted price.
aspect_ratioNoShape of the picture, for example 1:1 (square), 16:9 (wide), 9:16 (phone screen), 4:5 (portrait post). Default 1:1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Billing unit: USD for API keys; credits for OAuth (optional for existing OAuth clients).",
+  "type": "string"
+}
    • changedInput schema / properties / max_credits / description
      Previous value: -"The most credits the user agreed to spend on this. Only set it after the user confirmed a quoted price."New value: +"OAuth only: the most site credits the user agreed to spend on this. Only set it after the user confirmed a quoted price."
    • addedInput schema / properties / max_usd
      Added value: +{
+  "description": "API key only: maximum approved USD as a decimal string with up to 9 fractional digits. Set currency to USD. Only set after the user confirms the quoted cost_usd. Never convert max_credits.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (non-readOnly, non-idempotent, non-destructive), the description adds genuinely useful behavior: spend is charged in site credits under OAuth or USD under an API key, the tool quotes the price first, and it returns the picture plus a link. The cost/quote disclosure is exactly the kind of spending context annotations do not carry. It does not mention whether a job id is returned for polling, which is a minor gap.

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 zero filler: purpose first, then billing mechanics, then return value. Every sentence earns its place and the most decision-relevant fact (what the tool does) is front-loaded.

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 no output schema, the description correctly covers the return value (image plus link) and the cost/quote flow, which is the riskiest aspect of an irreversible spend. The remaining gap is execution model: the presence of get_job among siblings suggests possible asynchronous job submission, which the description does not address.

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 the schema already documents prompt, model, aspect_ratio, currency, max_credits and max_usd in detail. The description reinforces the currency/credits vs USD split and the quote-then-confirm flow but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

"Make a new picture from a description" states a specific verb (generate) and resource, and the phrase "new picture" implicitly separates it from edit_image, expand_image, upscale and remove_background. It stops short of naming those siblings explicitly, so differentiation is inferred rather than stated.

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 description conveys implied usage (generate a fresh image from a prompt) and explains the two billing modes, but gives no explicit when-to-use / when-not-to-use guidance against siblings like edit_image or create_video_from_references. An agent must infer the selection rule from the tool name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PopNow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources