Skip to main content
Glama
Sign In
@runapi.ai/gemini-omni-mcp

@runapi.ai/gemini-omni-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_pricing

Look up RunAPI pricing for Gemini Omni models by endpoint or action. Use it to confirm per-model costs before creating audio, character, or text-to-video tasks.

Instructions

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

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

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.3.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "gemini-omni-audio",
-  "gemini-omni-character",
-  "gemini-omni-flash-1-1",
-  "gemini-omni-flash-preview",
-  "gemini-omni-text-to-video"
-]
  2. Changed1 schema field changedv0.2.2
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "gemini-omni-audio",
-  "gemini-omni-character",
-  "gemini-omni-flash-preview",
-  "gemini-omni-text-to-video"
-]New value: +[
+  "gemini-omni-audio",
+  "gemini-omni-character",
+  "gemini-omni-flash-1-1",
+  "gemini-omni-flash-preview",
+  "gemini-omni-text-to-video"
+]
  3. Addedv0.2.1
  4. Removedv0.2.0
  5. First observedv0.1.0

TDQS

B3.1/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. It doesn't state that this is a read-only, non-mutating lookup, doesn't describe the shape or units of the pricing response, and gives no indication of rate limits or whether pricing varies by action/model combination.

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?

A single, front-loaded sentence with no filler or redundancy. Every word earns its place.

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?

The tool is simple (2 optional params, no output schema), and the schema covers both parameters, but the description omits any hint of what pricing data is returned or how the action parameter affects the result. Adequate as a minimum but with visible gaps.

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%, with both the model slug and action enum documented in the schema itself, so the baseline of 3 applies. The description adds no parameter-level meaning beyond restating the model line, and notably never mentions that an 'action' endpoint selector exists.

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'), and names the model scope explicitly. It's distinguishable from siblings like create_audio or get_task, though the 'gemini-omni model line' scoping sits oddly against parameters that accept arbitrary model slugs and action enums.

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?

No guidance on when to call this versus the sibling creation tools (e.g., as a pre-flight cost check before create_audio or text_to_video). The only implied usage is that pricing is discoverable, and no prerequisites or exclusions are stated.

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