Skip to main content
Glama

list_models

Lists hosted tiers and supported LLM key providers, including each tier's model, default reasoning, and per-task credits, so you can choose the correct setup.

Instructions

List the hosted tiers (browsa, browsa-fast, browsa-smart: the model each runs on, its default reasoning and credits per task) and the providers a saved or per-task LLM key can be for. Read-only and free.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does state the key traits directly: "Read-only and free." It also discloses the shape of what comes back (model, default reasoning, credits per task, provider list). It omits any note on caching or whether the tier list is static, but the safety and cost profile is fully covered for a no-parameter read.

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?

One sentence, front-loaded with the primary resource, with the enumerated detail packed into a parenthetical rather than sprawled across clauses. No filler and no restatement of the tool name.

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?

For a parameterless, read-only enumerator with no output schema, the description tells the agent both what categories are returned and the per-tier fields, plus that the call is free. Nothing needed to decide to call it or to interpret the result 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 zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. It correctly spends no words on inputs and instead describes outputs.

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?

Uses a specific verb ("List") over two named resources: hosted tiers (browsa, browsa-fast, browsa-smart) and the providers an LLM key can target. The parenthetical enumerates exactly what is reported per tier (model, default reasoning, credits per task), so an agent can tell this apart from list_llm_keys or credits without opening a schema.

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

Usage Guidelines3/5

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

Usage is implied by the content it returns — you call it to discover available tiers/models and valid key providers — but the description never states when to prefer it over siblings like list_llm_keys or credits, nor any preconditions. Adequate context, no explicit routing guidance.

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