Skip to main content
Glama
Sign In

NovAI Prices

by io.github.vvvvking
OverviewDiscussionsAdmin

cheapest_models

List the cheapest Chinese AI models from NovAI's live price feed, ranked by a comparable cost unit (text: 1M input + 200K output; video: 5-second clip; image: per image). Use this when the user asks which model is cheapest, wants to compare costs, or is choosing a model by budget. For a batch cost estimate at list price, see https://aiapi-pro.com/video-cost-calculator (video) and https://aiapi-pro.com/image-cost-calculator (images).

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

Input Schema

NameRequiredDescriptionDefault
limitNomax rows (default 10, max 50)
categoryNoVideo, Image, Chat / LLM, Audio, 3D, Embedding
max_priceNoonly models whose comparable cost is at or below this USD figure

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses the data source (live price feed) and the normalization scheme used for ranking, which is genuinely useful, but says nothing about read-only nature, freshness/caching, rate limits, or how ties or missing categories are handled.

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 core action and cost-unit definitions in the first sentence, then usage guidance, then the calculator pointers. Three sentences with little waste, though the two promotional URLs are the least essential part.

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 still tells the agent what the results represent (models ranked by a normalized comparable cost) and how each row's unit differs by category. Remaining gaps are minor: no field list, pagination, or freshness guarantees.

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 coverage is 100%, so baseline is 3; the description adds value by explaining that the comparable cost unit varies by category (1M input + 200K output for text, 5-second clip for video, per image), which clarifies why category and max_price interact with the ranking.

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 (List), resource (cheapest Chinese AI models), source (NovAI live price feed) and ranking basis (comparable cost unit with per-category definitions). It is unambiguous on its own, but it never names the siblings list_categories or model_price, so the agent must infer how it differs from model_price.

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?

Gives explicit trigger conditions: user asks which model is cheapest, wants to compare costs, or is choosing by budget. It also redirects to external cost calculators for batch estimates, but offers no guidance on when to prefer the sibling model_price instead.

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

All NovAI Prices toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources