Skip to main content
Glama

List every text model and price

list_models
Read-onlyIdempotent

Every chat, embedding, rerank and transcription model on PentestLLM with its id, type, the routes and tools that take it, our price (per million tokens, or per audio minute for transcription), the developer's list price where recorded, the wire formats it answers (openai, anthropic, gemini) and its specs. Image, video, speech, music and 3D models are in list_media_models. No key needed. Live from GET /v1/catalog.

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
typeNoOnly models of this type. Default: every text model.
searchNoA substring of the model id or name (opus, deepseek, uncensored...).
developerNoOnly models from this developer (Anthropic, OpenAI, Google, DeepSeek...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds real context beyond them: no API key required, data is live from GET /v1/catalog, and prices are per million tokens except transcription which is per audio minute. It also discloses the developer list price is only present 'where recorded', which sets expectations about partial data.

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 resource and its scope, then the sibling exclusion, then operational facts (no key, endpoint). The field enumeration is dense but each item describes an actual returned value, so little is wasted; only marginal tightening would help.

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 carries the burden of explaining the return shape, and it does so thoroughly — ids, types, routes/tools, both price figures, wire formats, and specs. Combined with the routing note and auth note, nothing material an agent needs is missing.

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 description coverage is 100%, so the three filters (type, search, developer) are already documented in the schema, including the enum and the default. The description mentions the type dimension only indirectly through the enumeration of model categories and adds no syntax hints for search or developer, so baseline 3 applies.

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+resource and enumerates the exact scope (chat, embedding, rerank, transcription) plus the fields returned (id, type, routes, price, wire formats). It explicitly credits the sibling list_media_models with the excluded model types, so an agent can separate the two 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 Guidelines4/5

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

Gives a clear exclusion rule — image, video, speech, music and 3D models live in list_media_models — which routes the agent correctly. It does not spell out the positive trigger (e.g. 'call this before chat/embed to find a model id'), so a small inference is left to the agent.

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.