Skip to main content
Glama

List public models

list_public_models
Read-onlyIdempotent

Find public Ubi models, scenarios and qualified browser operations without login. Results include next_offset pagination and browser links; this read runs no simulation.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
searchNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower; the description still adds non-obvious traits: no authentication needed, pagination surfaced as next_offset, browser links included, and no simulation executed. It does not mention rate limits or result-size caveats, so it stops short of 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?

A single dense sentence that front-loads the resource and keeps the access constraint and behavioral notes in the same breath; nothing is filler. Minor deduction for the vague jargon "qualified browser operations," which costs clarity without buying space.

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?

An output schema exists and annotations cover the safety profile, so the description needn't explain return values or side effects. What remains missing is parameter-level guidance for the three undocumented inputs, which is the only real gap for a simple discovery tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for limit, offset, and search — yet it never explains any of them. The only pagination mention refers to the output field next_offset, not the input offset, leaving search semantics (matching on name? owner? scenario text?) entirely unknown.

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?

States a specific verb ("Find") plus concrete resources: public Ubi models, scenarios, and qualified browser operations, with the valuable qualifier "without login". It does not explicitly contrast with the singular get_public_model / get_public_scenario_result siblings, so the list-vs-fetch distinction must be inferred from the name.

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?

"without login" and "this read runs no simulation" imply when this is the right entry point (anonymous discovery before fetching details), but there is no explicit when-to-use / when-not-to-use statement and no named alternative such as get_public_model. Usage is implied rather than prescribed.

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