Skip to main content
Glama

Snap: list available models

snap_list_models

Lists model IDs available to your SubQ API key so you can pick a valid model for decision tools and endpoints that require one.

Instructions

List the model IDs available to the configured SubQ API key (GET /v1/models, OpenAI-compatible shape). Use a returned id with the endpoint that supports that model; the Decisions tools in this server need a decision model such as subq-snap-1.2.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key traits that matter: results are scoped to the entitlements of the configured API key, and the payload follows an OpenAI-compatible shape, both of which are useful non-schema facts. It says nothing about auth failure modes, empty results, or error behavior, which is a notable gap for a zero-annotation tool.

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?

Two sentences, each load-bearing: the first defines what is returned and its source, the second tells the agent what to do with the result. The identifying information is front-loaded and there is no filler.

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 simple, argument-free read tool this is close to complete — it covers source, scoping, response shape, and downstream use. The only shortfall is that, with no output schema, the description does not say what fields accompany each model id beyond the OpenAI-compatible pointer, leaving return-value detail slightly thin.

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, so there is no parameter semantics to compensate for and the baseline applies. The description does not waste space restating an empty schema, which is appropriate.

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?

The description names a specific verb and resource ("List the model IDs") plus the exact upstream endpoint (GET /v1/models) and scoping ("available to the configured SubQ API key"). An agent can immediately tell this is a discovery/enumeration tool, distinct from the action-oriented siblings snap_choice/snap_decide/snap_score.

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 real downstream guidance: take a returned id and use it with the endpoint that supports that model, and it notes that the Decisions tools require a decision model such as subq-snap-1.2. That establishes when this tool is worth calling (before configuring a Decisions call). It does not explicitly say when not to call it or name a competing discovery tool, so it stops short of a 5.

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