Skip to main content
Glama

novai_pricing_feed

Retrieve the complete live AI model price leaderboard across all categories, ranked by normalized cost, to build model comparisons and cost tables.

Instructions

Return the complete live price leaderboard (all categories, models ranked by normalized cost).

Use for comparisons or cost tables. For one quick answer use novai_cheapest instead. Returns {generated_at, categories: [{category, models: [{name, price_usd, unit, url}]}]}. Units differ (per 1M tokens / per generation / per image / flat) - always compare by unit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral load, and it does disclose the return shape, that prices are live (with a generated_at stamp), and a critical usage caveat that units differ by category and comparison must be unit-aware. It stops short of stating pagination, caching/freshness guarantees, or auth needs, which is the only reason it isn't 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?

Four short lines, each doing distinct work: purpose, use case, alternative routing, return shape, and a units warning. Front-loaded with the purpose and free of filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description inlines the return structure ({generated_at, categories: [{category, models: [...]}]}) and flags the unit heterogeneity that would otherwise cause an agent to miscompare costs. For a zero-parameter read-only tool, nothing material is missing.

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?

The input schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its words on return-value semantics, which is the right use of space here.

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 — "Return the complete live price leaderboard" — and immediately scopes it as "all categories, models ranked by normalized cost." The breadth of "complete/all categories" is exactly what separates it from the sibling novai_cheapest, so an agent can pick between them without opening the schema.

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?

Gives the affirmative case ("Use for comparisons or cost tables") and the negative case with a named alternative ("For one quick answer use novai_cheapest instead"). The routing condition is explicit rather than inferred.

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