Skip to main content
Glama

Find models

find_models
Read-onlyIdempotent

Find catalog models (CPUs, graphics cards, phones, consoles) by name. Returns slugs to use with get_model_prices, estimate_fps and check_build.

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": {
      "query": "<query>"
    },
    "name": "find_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryYese.g. 'RTX 3060', 'Ryzen 7 5800X3D', 'iPhone 13'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world scope, so safety is covered. The description adds behavior beyond that: the result is a set of slugs (a return contract, valuable since there is no output schema) and it enumerates the bounded catalog domain, consistent with openWorldHint=false. It omits matching behavior (exact vs fuzzy) and no-match handling.

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, zero filler, and the most decision-relevant information (what it finds and what it returns) is front-loaded. The downstream-tool pointer is a single compact clause rather than a paragraph.

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 three-parameter read-only lookup with annotations covering its safety profile, the description supplies purpose, domain and return contract. The remaining gaps — default value and effect of 'limit', and whether matching is fuzzy or exact — are minor but real, especially with no output schema to fall back on.

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?

Schema coverage is 33%: only 'query' is documented in the schema, while 'kind' and 'limit' have no schema descriptions. The description partially compensates by mapping the catalog categories to the kind values ('graphics cards' for gpu) and reinforcing that query is a name, but it never mentions 'limit' or whether 'kind' filters or merely hints.

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?

Names a specific verb ('Find') and a specific resource ('catalog models'), enumerates the four categories in scope (CPUs, graphics cards, phones, consoles), and states the matching key ('by name'). It also names the downstream tools that consume its output, so an agent can place it precisely among siblings like get_model_prices and check_build without opening any schema.

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?

Positions the tool as the first step in a workflow by saying the returned slugs are for get_model_prices, estimate_fps and check_build, which is effectively a when-to-use instruction. It does not say when not to use it (e.g. versus search_listings or get_listing for non-catalog items), so the guidance is clear but not exhaustive.

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