Skip to main content
Glama

Smarty Pants

Find a model

find_model
Read-onlyIdempotent

Find Smarty Pants models that fit a task and constraints (context size, max price, needed features, available now). Returns matches cheapest first, or a suggestion to request a model if none fit. 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": "find_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat the model is for, in plain words
needsNoFeatures the model must support
available_nowNoOnly models that can serve a request right now
min_context_tokensNo
max_output_price_per_million_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: results are ranked cheapest first, and a failure to match yields a suggestion to request a model rather than an empty result. 'No sign-in needed' also removes an auth precondition the agent would otherwise have to discover. It does not mention pagination or result limits, a minor gap.

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?

Three short sentences with the core purpose front-loaded and the return-shape and auth facts appended in order of decreasing importance. Tight and readable, with only 'no sign-in needed' sitting slightly oddly at the end rather than near the top.

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, so the description carries the return-value burden and does so adequately by describing the ordering (cheapest first) and the no-match alternative. For a five-parameter read-only search tool this is nearly complete; only result count/pagination behavior is left unstated.

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?

The description enumerates the constraint families (context size, max price, needed features, available now, task), which maps onto the five parameters and gives a little interpretive value. With 60% schema coverage the schema already documents most fields, and the description adds no format or interaction details (e.g., how needs combines with available_now), so the baseline 3 applies.

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 ('Find Smarty Pants models') plus the qualifying dimensions (context size, price, features, availability), which is far more than a restatement of the name. It does not explicitly distinguish itself from the sibling list_models, so an agent must infer that this is a constraint-driven search rather than a full catalog dump.

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?

Clearly frames the use case as matching a model to a task and constraints, and names the downstream alternative ('a suggestion to request a model if none fit'), which routes the agent to request_model on failure. It stops short of stating when to prefer this over list_models or estimate_cost.

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