Skip to main content
Glama

List Recipe Models

list_recipe_models
Read-onlyIdempotent

List models available to recipe authoring.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no statement about result size, pagination behavior, ordering, or whether the list is filtered by workspace/tenant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler and the resource front-loaded, so it is not bloated. However, brevity here comes at the cost of under-specification rather than efficiency — the sentence is too thin to be actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, but the definition still omits pagination semantics for a 2-parameter paginated list and never clarifies what a 'model' is in this system. For a discovery tool that likely gates downstream authoring, that leaves the agent guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (limit with min 1/max 25, cursor with maxLength 512) have zero schema description coverage, and the description says nothing about them. The agent cannot tell from the definition that this is a paginated endpoint or that limit is capped at 25, so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb (List) and a resource (models available to recipe authoring), but 'models' is undefined — it could be AI/LLM models, recipe template models, or data models. The phrase 'available to recipe authoring' hints at scope but does not tell an agent what kind of entity is returned, so the purpose is only vaguely distinguishable from the many other list_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of an alternative tool or the conditions that would select one. The agent must infer that this is a discovery/enumeration call performed before authoring a recipe.

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