Skip to main content
Glama

Makes and models in stock

list_makes_and_models
Read-onlyIdempotent

Makes (and optionally models of one make) currently in stock with counts and the matching motifyme.co hub page url.

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_makes_and_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeNooptional: a make to list models for

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's burden is lighter. It still adds value by disclosing the response contents — per-make counts and a matching hub page URL — which matters because no output schema exists. It omits ordering, pagination, or what happens when a make has no stock.

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?

A single dense sentence with no filler; the primary resource is front-loaded and the return contents follow immediately. Nothing is repeated from the title beyond necessary context.

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 one-optional-parameter read tool with rich annotations, the description covers purpose, both modes of use, and the shape of the result despite no output schema. Missing only edge-case behavior (empty results, ordering) to be fully complete.

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 100% and the single `make` parameter is already documented as 'a make to list models for', so the schema carries most of the weight. The description's 'optionally models of one make' reinforces the behavioral effect of supplying it (mode switch from make list to model list) but adds no format, casing, or matching rules.

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?

The description names a specific resource (makes currently in stock) and a concrete return payload (counts plus the motifyme.co hub page url), so an agent knows exactly what it gets back. It clarifies the optional narrowing to models of one make. It does not explicitly contrast itself with siblings such as search_marketplace, so it stops short of a 5.

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 implied rather than stated: calling with no argument returns makes, calling with a make returns that make's models. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for listing inventory.

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