Skip to main content
Glama
Sign In
runapi-ai

RunAPI Gemini TTS MCP Server

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_pricing

Retrieves RunAPI pricing for the gemini-tts model line so you can confirm text-to-speech costs before generating audio.

Instructions

Look up RunAPI pricing for the gemini-tts model line.

Input Schema

NameRequiredDescriptionDefault
modelNoModel slug. Defaults to the line's primary model.
actionNoEndpoint name. Defaults to the endpoint that offers the model.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "gemini-2.5-pro-tts",
-  "gemini-3.1-flash-tts"
-]
  2. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it says nothing about this being a read-only operation, whether pricing is live or cached, what currency or billing units apply, or whether authentication/rate limits matter. For a simple lookup the risk is low, but the disclosure gap is real.

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?

A single front-loaded sentence with no filler; the scope constraint comes first. It is efficient rather than padded, though it omits useful context rather than wasting words.

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?

For a 2-optional-parameter lookup with no output schema, the description should indicate what the return value contains (e.g., per-unit rates, currency). It states the subject but leaves the response shape and pricing units unaddressed.

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 coverage is 100%, so both `model` and `action` are already documented in the schema. The description adds no format details (slug syntax, what other values are valid, what 'primary model' means) beyond the schema, so 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?

States a specific verb ('Look up') and resource ('RunAPI pricing'), scoped to the gemini-tts model line, which is enough to separate it from login, text_to_speech, and get_task. It does not, however, reconcile the fixed 'gemini-tts model line' scope with the schema's free-form `model` parameter.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use, when-not, or alternative-tool guidance. Any inference (e.g., call this before text_to_speech to estimate cost) is left entirely to the agent.

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

Deploy Server

Other Tools