Skip to main content
Glama

novai_transparency

Returns NovAI's platform billing and policy metrics—platform fee, price multiplier, refund policy, rate limits, and billed units—for questions about how billing and pricing policy works.

Instructions

Return NovAI's published platform metrics: 0% platform fee, 1.0x price multiplier, refund policy, rate limits and billed units.

Use when the user asks how billing or pricing policy works. For actual model prices use novai_pricing_feed. Returns a JSON object.

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

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?

No annotations are provided, so the description carries the burden; it signals a read-only informational source ('published platform metrics') and states the return type ('Returns a JSON object'). It does not address freshness/caching of the metrics or whether any auth is required, which is the only remaining gap for a zero-param read tool.

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 sentences: content first, usage trigger second, sibling disambiguation third. No filler, and the most decision-relevant routing information is front-loaded.

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?

With no output schema, the description compensates by enumerating the fields the JSON object contains, and it names the sibling to use for the adjacent need. Nothing an agent needs to call this zero-param tool correctly 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 tool takes no parameters, so there is nothing to disambiguate; the baseline applies. The description instead usefully documents the conceptual payload (fee, multiplier, refund policy, rate limits, billed units) in place of parameter detail.

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 NovAI's published platform metrics') and enumerates exactly what is covered: platform fee, price multiplier, refund policy, rate limits, billed units. It explicitly distinguishes itself from the pricing sibling by scoping itself to policy rather than model prices.

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 asks how billing or pricing policy works') and an explicit exclusion with the alternative named ('For actual model prices use novai_pricing_feed'). The agent can route between the two without inspecting either schema.

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