fal.ai MCP Server

pricing

Retrieve unit pricing with currency for specific model endpoints. Get pricing based on output per image or video.

Instructions

Get pricing information for specific model endpoint(s). Returns unit pricing with currency. Requires authentication. Most models use output-based pricing (per image/video).

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": {
      "endpoint_ids": "<endpoint_ids>"
    },
    "name": "pricing"
  }
}

Input Schema

Name	Required	Description	Default
`endpoint_ids`	Yes	Endpoint ID(s) to get pricing for (e.g., ['fal-ai/flux/dev']). Must provide at least 1 endpoint ID (1-50 models).
`cursor`	No	Pagination cursor from previous response (for next page)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.4Jun 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description bears full responsibility. It discloses authentication requirement and notes that most models use output-based pricing, which adds behavioral context. However, it lacks details on rate limits, pagination behavior beyond cursor, or any side effects.

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?

The description is very concise with four short sentences. The key verb 'Get' is front-loaded, and every sentence contributes meaning without redundancy.

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?

While adequate for a simple read tool, the description lacks details on the return format or structure (e.g., what keys are in the response). Since there is no output schema, the agent may need more information to process the result correctly.

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 100%, and the description adds value by clarifying constraints: 'Must provide at least 1 endpoint ID (1-50 models)' and 'for next page' on cursor. This goes beyond the schema's basic descriptions.

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?

The description clearly states the tool retrieves pricing information for model endpoints, including unit pricing and currency. It distinguishes itself from sibling tools like 'estimate_cost' and 'usage' by focusing on endpoint-specific pricing. However, it could be more specific about the exact fields returned.

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 mentions authentication is required but provides no guidance on when to use this tool versus alternatives like 'estimate_cost' or 'usage'. There is no mention of when-not-to-use or context for selection.

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

Deploy Server