Skip to main content
Glama

Get public model

get_public_model
Read-onlyIdempotent

Read a public model's scenario inputs, units, limitations, source hashes and exact browser qualification. Returns browser_url for qualified no-signup simulation or scans; this read executes no model.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model_id": "<model_id>"
    },
    "name": "get_public_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the description adds real value beyond them: it says the call returns a browser_url for qualified no-signup simulation or scans, and explicitly clarifies 'this read executes no model' — a meaningful disclosure that the returned URL is not an execution.

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?

Two tight sentences with the resource and returned content front-loaded and the non-execution caveat placed last for emphasis. The enumerated return fields partially overlap the existing output schema, but no sentence is wasted.

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?

With an output schema covering return values and annotations covering safety and idempotency, the description only needs to establish what the call reads and that it triggers no execution — both are present. Only the single-parameter semantics remain thin.

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?

Only one parameter (model_id) at 0% schema coverage, so the description must carry the semantic load. It does scope the argument to a *public* model, implying the ID must reference a publicly listed model, but adds nothing about the identifier format beyond what the regex already encodes.

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 ('Read') and resource ('a public model') and enumerates the content it exposes: scenario inputs, units, limitations, source hashes and browser qualification. An agent can tell this is a per-model detail read rather than a listing call, though no sibling is named.

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 only implied: fetch one public model by ID to inspect its inputs and qualification status. There is no explicit when-to-use or when-not-to-use guidance versus list_public_models or get_public_scenario_result, so the agent must infer the boundary.

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