Skip to main content
Glama
io.github.vvvvking/novai-prices-mcp

io.github.vvvvking/novai-prices-mcp

cheapest_models

Find low-cost Chinese AI models from a live price feed, ranked by comparable cost units for text, video, and image workloads; filter by category or maximum USD price.

Instructions

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).

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)
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 observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the live price feed and defines the comparable cost units for text, video, and image, but omits other behavioral traits such as read-only safety, pagination/default behavior, authentication needs, and return format.

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 definition is a single front-loaded sentence with no wasted wording. The parenthetical ranking definitions are compact and directly useful for interpreting the comparable cost.

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 simple three-parameter read-only list tool, the description covers the core purpose and ranking methodology. However, with no output schema and no annotations, it leaves gaps around return fields, sibling-tool selection, and some behavioral details.

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%, so the input schema already documents limit, category, and max_price. The description adds no parameter-level meaning beyond that, making the baseline 3 appropriate.

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 uses a specific verb ('List') and resource ('cheapest Chinese AI models') and identifies the source ('NovAI's live price feed') plus the ranking basis. It does not explicitly distinguish itself from sibling tools such as model_price or list_categories.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any when-not conditions or prerequisites. The intended use is only implied by the name and the word 'cheapest'.

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