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

io.github.vvvvking/novai-prices-mcp

list_categories

Returns the model categories in NovAI’s live price feed, enabling category-based filtering when comparing Chinese AI model prices.

Instructions

List the model categories available in NovAI's price feed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden. "List" implies a read, but nothing is said about the return shape (there is no output schema), whether categories are static or dynamic, or if results are paginated or cached, which leaves an agent guessing about behavior.

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 front-loaded sentence with no filler, correctly sized for a zero-parameter read tool.

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?

The description is adequate for a trivial zero-param tool, but because annotations and an output schema are both absent, an agent gets no picture of the return value or of how this tool fits alongside its two siblings.

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?

With zero parameters, there is nothing for the description to disambiguate, which is the baseline-4 case. The description correctly makes no attempt to invent parameter semantics.

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 verb is specific ("List") and the resource is precisely scoped ("model categories available in NovAI's price feed"), so an agent knows exactly what it returns. It does not differentiate itself from the siblings cheapest_models and model_price, 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?

The phrase "categories available" implies a discovery-first use case, but the description never says when to call this rather than model_price or cheapest_models, nor whether its output feeds into those tools. Usage is only implied.

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