Skip to main content
Glama
Sign In

Emero

by io.github.EmeroAI
OverviewDiscussionsAdmin

Model price list

get_pricelist
Read-onlyIdempotent

Read-only. Every emero model and its per-generation cost in USD, from the live at-cost rate card (zero markup). Optional filters: kind (image/video/music/speech/edit) and model (exact id). Each model lists its price tiers (quality / resolution / duration / sound) with the unit basis — per image, per second of output, per generation, or per 1,000 characters. Use it when the user asks what something costs or wants the full price list. Changes 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": "get_pricelist"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
modelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description's value is in adding that prices come from a live at-cost rate card with zero markup and that each model exposes tiered pricing with a unit basis. That is real context beyond the annotations; the closing 'Changes nothing' largely repeats the readOnlyHint rather than adding new information.

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?

Front-loaded with the read-only constraint and the resource, then filters, then the return shape, then the trigger. Four tight sentences with little waste, though 'Changes nothing' is redundant padding given the annotations.

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?

With no output schema, the description steps in to explain the return shape: per-model price tiers keyed by quality/resolution/duration/sound plus the unit basis (per image, per second, per generation, per 1,000 characters). An agent can both decide to call it and interpret the result without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 carry the burden, and it does: kind is described as the media kind filter and model as an exact id. It enumerates the kinds (image/video/music/speech/edit), which duplicates the schema enum, and could say whether filters are combinable, but otherwise the parameters are fully interpretable.

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: reads every emero model and its per-generation cost in USD from the live at-cost rate card. No sibling tool touches pricing, and the scope (all models, optional narrowing) is unambiguous.

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?

Explicitly says to use it when the user asks what something costs or wants the full price list, which is a clear trigger condition. It does not name an alternative or exclusion, though none of the siblings plausibly compete with it for pricing questions.

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

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