Postemi: Social Media Scheduler

fotoai_quote

Read-only

The exact price of a FotoAI generation in the user's FotoAI credits, and their balance. Nothing is spent.

Tell the user the price (credits) and ask before calling fotoai_generate with the returned quote_id; it is valid for 10 minutes. If insufficient is true, give the user the topup_url instead of generating.

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": {
      "model": "<model>"
    },
    "name": "fotoai_quote"
  }
}

Input Schema

Name	Required	Description
`model`	Yes	A model id from fotoai_list_models.
`aspect`	No	Aspect ratio, e.g. "1:1", "4:5", "9:16", "16:9", from the model params.
`params`	No	Other model parameters by key, e.g. { "resolution": "2K" }.
`prompt`	No	What to generate, in any language.
`duration`	No	Video length in seconds (video models only).

Output Schema

Name	Required	Description	Default
`error`	No
`output`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Consistent with readOnlyHint=true and destructiveHint=false, and it adds behavior the annotations don't: nothing is charged, the quote expires in 10 minutes, and an insufficient balance routes to a topup_url. It omits auth/rate-limit context, keeping it just short of 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 with zero padding. The key constraint ('Nothing is spent') is front-loaded, followed by the required workflow and the failure branch.

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

Completeness5/5

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

An output schema exists, yet the description still surfaces the operationally critical return fields (quote_id, insufficient, topup_url) and their implications. Nothing an agent needs to call this correctly or act on the result is missing.

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 model, aspect, params, prompt, and duration. The description mentions only the returned quote_id and adds no syntax or format detail for the five inputs, so baseline 3 applies.

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: retrieves the exact credit price of a FotoAI generation plus the user's balance. The phrase 'Nothing is spent' cleanly separates it from fotoai_generate, so an agent can distinguish it without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit sequencing: tell the user the price, ask for confirmation, then call fotoai_generate with the returned quote_id. It also names the branch condition (insufficient is true) and the alternative action (give topup_url instead of generating).

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

All Postemi: Social Media Scheduler tools Inspect

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.