Skip to main content
Glama

ai_catalog

Read-onlyIdempotent

List every AI model the platform offers — feature, model id, provider, pricing string, and whether it's free for Builders. Paid-model rates vary by plan and are listed at /v1/pricing. It lists what is available before a model is chosen for ai_complete, ai_tts, ai_generate_image, ai_remove_background, or embeddings.

Read-only. No activation needed.

Example:

{}
// Returns: { "free_tier": { ... }, "markup_rate": 0.05, "models": [{ "feature": "tts", "model": "hexgrad/Kokoro-82M", "provider": "deepinfra", ... }, ...] }

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds 'No activation needed', which is real operational context an agent would otherwise have to discover. It also discloses a pricing caveat — paid rates vary by plan and live at /v1/pricing — so the agent knows the returned pricing string may not be the final charge. No rate-limit or auth detail, hence not 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and returned fields, then the usage pointer, then a compact operational note. The embedded JSON example earns its space because there is no output schema. Minor redundancy between 'pricing string' and the /v1/pricing caveat keeps it from a 5.

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 parameters, no output schema, and only read-only annotations, the description carries the remaining burden well: it lists the returned fields, sketches the response envelope (free_tier, markup_rate, models[]) in the example, and flags the pricing caveat. An agent has everything needed to call it correctly and interpret the result.

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; baseline 4 applies. The empty-object example (`{}`) usefully confirms the caller passes no arguments at all.

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 AI model the platform offers') and enumerates the fields returned: feature, model id, provider, pricing string, free-for-Builders flag. It also distinguishes itself from the sibling tools that consume the catalog (ai_complete, ai_tts, ai_generate_image, ai_remove_background, embeddings), so an agent knows this is the discovery step, not an inference call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: call this before choosing a model for ai_complete, ai_tts, ai_generate_image, ai_remove_background, or embeddings. That is a concrete when-to-use signal tied to named siblings. It stops short of explicit exclusions (e.g. 'do not use this to check spend — use ai_usage'), so it lands at 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources