Skip to main content
Glama
Sign In

Postemi: Social Media Scheduler

by com.postemi
OverviewDiscussionsAdmin

fotoai_list_models

Read-onlyIdempotent

The FotoAI (fotoai.hu) image and video models the user can generate with, using the user's OWN FotoAI account and credits.

Each model lists its id (pass it to fotoai_quote and fotoai_generate), whether the user's FotoAI account may use it (can_use), its parameters with allowed values and defaults (aspect, resolution, duration for video), and a base price in credits. Only suggest models with can_use true. Always call fotoai_quote for the real price before generating.

If FotoAI is not connected, the answer says where the user connects it.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOnly image or only video models. Both when omitted.

Output Schema

NameRequiredDescriptionDefault
errorNo
outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and openWorldHint. The description adds useful context beyond that: it explains the account/credit dependency, the can_use flag, and how the returned parameters and base price should be interpreted.

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?

The description is front-loaded with the core purpose, followed by output and usage guidance, then the connection fallback. It is appropriately sized, though the middle sentence is somewhat dense and partially overlaps with the output schema.

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?

Given the simple one-parameter schema, existing output schema, and rich annotations, the description covers everything an agent needs: purpose, usage constraints, downstream routing, and the disconnected-account path. No critical gap remains.

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%, and the single category parameter is fully documented with an enum and description. The tool description does not add meaning beyond the schema for that parameter, so it meets the baseline of 3 when the schema does the heavy lifting.

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?

The description states a specific verb and resource: it lists FotoAI image and video models available to the user's own account. It distinguishes the tool from sibling operations such as fotoai_quote and fotoai_generate by explaining that model ids are meant to be passed to those tools.

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 clear operational guidance: only suggest models with can_use true, and always call fotoai_quote for the real price before generating. It also covers the disconnected-account case. It does not explicitly compare against all alternatives, but the routing to quote and generate is explicit.

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 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