Skip to main content
Glama

List models

list_models
Read-onlyIdempotent

The AI models (chat, images or audio) available through SingIt, with their prices. Chat models can be called with chat or through SingIt's OpenAI-compatible API at https://app.singitai.app/v1. Search the returned list by id for models and prices. Paid calls stay inside owner-set key/allowance limits; check get_allowance before spending. Free, no key needed.

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

Input Schema

NameRequiredDescriptionDefault
kindNoDefaults to chat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the call is free and needs no key, results include prices, and paid downstream calls are bounded by owner-set key/allowance limits with a pointer to get_allowance. It does not describe pagination or result size, which is the main remaining gap.

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?

The purpose is front-loaded in the first sentence and the follow-on sentences each carry distinct operational information (endpoint, allowance check, free/no-key). There is minor redundancy between 'with their prices' and 'search the returned list by id for models and prices', but no filler overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter read tool with no output schema, the description covers what comes back (models plus prices, searchable by id), the cost model (free, no key), and the follow-on constraint (allowance limits). Only return shape and pagination are unaddressed, which is acceptable given the tool's simplicity.

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

Parameters3/5

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

Schema coverage is 100% and the single 'kind' parameter already carries its enum and default, so the schema does the heavy lifting. The description restates the three kinds (chat, images, audio) without adding selection guidance such as which kind to use for a given task. Baseline 3 applies when the schema fully documents the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (the chat/images/audio models available through SingIt) and adds that prices are included, so an agent knows this is a model catalog lookup. It is clearly distinct from the sibling 'chat' (which invokes a model) and from 'list_price_symbols' (crypto prices), though the distinction is implied by the resource wording rather than stated outright.

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?

It gives concrete usage context: check get_allowance before spending, use 'chat' or the OpenAI-compatible endpoint at https://app.singitai.app/v1 to actually call chat models, and no key is needed because listing is free. No explicit when-not-to-use case is given, but the intended workflow (list -> check allowance -> chat) is easy to infer.

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.