Skip to main content
Glama
Sign In
ai-api-prices

ai-api-prices

by Liutasil501
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find AI models

find_models
Read-only

Search AI API models by name or keyword across text, image, video, speech, search, and embedding categories to find each match's cheapest USD price and provider.

Instructions

Search AI API models by name across text (LLMs), image, video, transcription, tts, search, and embedding categories, returning up to 10 matches with each model's cheapest USD price and provider. Exact slug or prefix matches rank first, then widely sold models. Use model_prices to list every provider for a matched model, or cheapest_models to browse lowest prices in a category.

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": {
      "query": "<query>"
    },
    "name": "find_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesModel name, slug, or keyword, e.g. "gpt-oss", "claude sonnet", or "flux".
categoryNoOptional category filter: text (LLMs), image, video, transcription (speech-to-text), tts (text-to-speech), search (web search), or embedding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / category / description
      Previous value: -"text (LLMs), image, video, transcription, tts, search or embedding"New value: +"Optional category filter: text (LLMs), image, video, transcription (speech-to-text), tts (text-to-speech), search (web search), or embedding."
    • changedInput schema / properties / query / description
      Previous value: -"Model name or part of it, e.g. \"gpt-oss\", \"claude sonnet\", \"flux\""New value: +"Model name, slug, or keyword, e.g. \"gpt-oss\", \"claude sonnet\", or \"flux\"."
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds genuinely new behavioral detail: a hard cap of 10 results, a ranking policy (exact slug or prefix matches first, then widely sold models), and the two fields returned per model. It doesn't state what happens on zero matches or whether price is per-token or per-million, which keeps it below a 5.

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?

Two dense sentences, zero padding, with capability and result shape front-loaded and the sibling routing deferred to the end where it belongs. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 usefully specifies the return contents and the 10-result cap, which is more than most search tools offer. The remaining gap is the ambiguity of 'cheapest USD price' (unit of measure) and unstated empty-result behavior — minor for a read-only discovery tool.

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% and both parameters carry their own descriptions and an enum, so the schema does the heavy lifting. The description's category list merely restates the enum values and adds no format, matching, or ranking nuance beyond what is already structured.

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 ('Search AI API models by name') and enumerates the covered categories (LLMs, image, video, transcription, tts, search, embedding). It goes further by stating the result shape (up to 10 matches with cheapest USD price and provider), so an agent knows exactly what this returns versus the sibling pricing tools.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use model_prices to list every provider for a matched model, and cheapest_models to browse lowest prices in a category. The implied selection condition — you have a name/slug and need to resolve it — is stated in the first clause, so nothing is left to inference.

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