Skip to main content
Glama

novai_free_models

Lists the five zero-cost GLM Flash models on NovAI for text, vision, image, and video, helping users find free-tier options for zero-cost AI calls.

Instructions

List the 5 models that are free to call on NovAI (GLM Flash family: text, vision, image, video).

Use when the user wants zero-cost calls. These models are charged $0 but have a free-tier rate limit (10 free-model calls/day, 5 requests/min). For the full paid+free catalogue use novai_list_models. Returns a list of model ids.

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_free_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 full burden and does well: it discloses pricing ($0), free-tier limits (10 calls/day, 5 req/min), and that the result is a list of model ids. It stops short of describing failure behavior when the rate limit is hit or any auth requirements, which keeps it from 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 sentences, front-loaded with the core action and count, followed by the usage rule, the rate-limit caveat, and the alternative. No filler or repetition.

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?

Simplest possible call signature, and the description still covers cost, rate limits, and sibling routing. An output schema exists so return values needn't be explained, and the mention of 'list of model ids' is a bonus rather than a crutch.

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 the schema-coverage baseline of 4 applies. The description correctly implies no filtering or pagination arguments are needed, consistent with the 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 the 5 models that are free to call on NovAI') and even enumerates the family (GLM Flash: text, vision, image, video). It explicitly contrasts with the sibling novai_list_models, so an agent can disambiguate without opening either 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 an explicit trigger ('Use when the user wants zero-cost calls') and names the alternative tool plus the condition that selects it ('For the full paid+free catalogue use novai_list_models'). Both the when and the when-else are covered.

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