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

io.github.vvvvking/novai-prices-mcp

model_price

Find the NovAI list price for an AI model by name fragment, such as seedance, kimi, glm, or qwen, to compare model costs.

Instructions

Look up the NovAI list price of a model by name fragment (seedance, kimi, glm, qwen...).

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": {
      "model": "<model>"
    },
    "name": "model_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/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 burden. It discloses the important behavioral detail that matching is by name fragment rather than exact ID, which implies substring/fuzzy matching. It says nothing about what happens with multiple or zero matches, whether the price is per-token or per-request, or the currency/units.

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 sentence with the operation front-loaded and the examples appended as a clarifying parenthetical. No filler.

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 one-parameter read-only lookup with no output schema, the description covers the what and the input form adequately. It is incomplete on the output side: units/currency of the 'list price' and whether ambiguous fragments return one match or a list are left unknown.

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 0% and the single 'model' parameter has no schema description, so the description must compensate — and it does, clarifying that the value is a name fragment and giving four concrete example fragments. It still doesn't say whether partial matches are resolved to one model or many.

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 ('NovAI list price of a model'), and the parenthetical examples (seedance, kimi, glm, qwen) make the domain concrete. It doesn't explicitly differentiate itself from the siblings cheapest_models or list_categories, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for pricing one specific model, versus cheapest_models for ranking by cost. There is no explicit statement of when to prefer this tool or what to do when the name is unknown.

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