Skip to main content
Glama

novai_list_models

Lists all model IDs available on the NovAI gateway to help users discover which models exist and choose one for chat or image tasks.

Instructions

List every model id available on the NovAI gateway (111 models).

Use when the user asks which models exist. For zero-cost models use novai_free_models; for prices use novai_cheapest or novai_pricing_feed. Returns a sorted list of model id strings (no prices).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

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 carries the load and does disclose the return shape (sorted list of model id strings) and an important negative trait (no prices included), which prevents an agent from misusing it for cost queries. It stops short of stating that the call is read-only with no side effects, and gives no latency, auth, or caching context.

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?

Three short lines, front-loaded with the core action and scope before the routing advice. Every sentence, including the no-prices caveat, carries informational weight with no redundancy.

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?

A zero-parameter listing tool with an output schema is about as simple as it gets, and the description still covers scope, count, output format, and sibling routing. Nothing an agent needs in order to call this correctly is absent.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The parenthetical model count gives the agent a sense of result size, which is a small value-add beyond an empty schema.

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 (list every model id on the NovAI gateway) and quantifies scope with the 111-model count. An agent can immediately distinguish this enumeration tool from novai_chat, novai_generate_image, or the pricing siblings.

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?

Explicitly names the triggering condition ('when the user asks which models exist') and routes to alternatives by task: novai_free_models for zero-cost, novai_cheapest or novai_pricing_feed for prices. This is textbook when-to-use/when-to-use-something-else guidance.

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