Skip to main content
Glama

Smarty Pants

List models

list_models
Read-onlyIdempotent

List the open models Smarty Pants serves on Apple Silicon Macs, with exact model ids, prices per million tokens, context size, features and whether each can serve a request right now. No sign-in needed.

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 observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds real value beyond them: no authentication is required and each entry reports live availability ('whether each can serve a request right now'), which the annotations cannot express.

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 front-loaded sentence that names the action first and then enumerates what comes back. It is dense but every clause (platform, fields, availability, no sign-in) carries information; minor cost is the long list-style enumeration.

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?

There is no output schema, and the description compensates by enumerating the key returned fields and the availability flag, so an agent knows what it will get. For a parameterless read tool this is close to complete; only a note on pagination or ordering would improve it.

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 the baseline is 4; the description correctly implies there is nothing to filter or configure. It also clarifies that the result is an unfiltered enumeration of all served models.

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 and resource ('List the open models') plus the concrete scope (models served on Apple Silicon Macs) and the returned fields (ids, prices, context size, features, availability). It is clearly a catalog-listing tool, distinguishable by name from find_model, though it never contrasts itself with siblings explicitly.

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?

The 'No sign-in needed' clause implies this is the public, no-auth entry point, which is useful usage context. However, there is no explicit statement of when to prefer this over find_model or estimate_cost, so the agent must infer that from the verb.

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