Skip to main content
Glama

novai_cheapest

Find the lowest-priced model in a chosen category by querying the live price leaderboard, returning its name, price, unit, and URL.

Instructions

Return the cheapest model in one category from the live price leaderboard.

Args: category: one of "Chat / LLM", "Image", "Video", "3D", "Audio", "Embedding" (default "Chat / LLM"). Returns a single model record with name, price_usd, unit and url. Use novai_pricing_feed when you need the full ranked feed across all categories.

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_cheapest"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoChat / LLM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.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 must carry the full behavioral burden. It describes the return format ('a single model record with name, price_usd, unit and url') and the read-only nature is implied by 'Return,' but it lacks explicit safety, rate-limit, or data freshness details. For a simple read tool, this is adequate but not comprehensive.

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 description is front-loaded with purpose, then logically presents arguments, return values, and the alternative tool. Every sentence is informative and there is no wasted text.

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?

For a simple one-parameter tool with no output schema and no annotations, the description covers all essential aspects: purpose, allowed parameter values and default, return fields, and an alternative for broader needs. Nothing critical is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by listing all allowed category values and the default ('Chat / LLM'). This gives the agent everything needed to supply the parameter correctly.

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 ('Return'), resource ('cheapest model'), scope ('in one category'), and source ('live price leaderboard'), and explicitly distinguishes itself from the sibling novai_pricing_feed. An agent can immediately understand what this tool does and how it differs from the full-feed alternative.

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?

Provides an explicit alternative and the condition for using it: 'Use novai_pricing_feed when you need the full ranked feed across all categories.' This implicitly defines when to use this tool (when you need only the cheapest model in a single category), giving clear routing guidance.

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