Skip to main content
Glama

Read recipes

AccountRecipesReadTool
Read-onlyIdempotent

Recipes other users published: search them, read one and how it installs, or read its markup.

  • searchRecipes: Search published recipes — params: query (query), sort_by (query: one of newest, oldest, popularity, trending, install, fork), limit (query), page_size (query), cursor (query)

  • getRecipe: Read a recipe and how it installs — params: id (path)

  • getRecipeMarkup: Read the markup of a recipe — params: id (path), sizes (query)

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": {
      "action": "<action>"
    },
    "name": "AccountRecipesReadTool"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesThe API operation to run
paramsNoThe operation's path, query and body parameters by name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/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 covered. The description adds that recipes are published by other users and that getRecipe includes install information, but it does not describe return format, pagination behavior, or cursor semantics.

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?

The description is front-loaded with the resource scope and immediately follows with a tightly formatted bullet list of actions and parameters. Every line contributes to action selection or invocation, with no filler.

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 multi-action read tool with no output schema, the description covers action selection and operation-specific parameters well. It omits return-value shape and pagination details, but it provides enough information for an agent to invoke the correct operation with the correct params.

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 top-level schema only exposes a generic 'action' enum and an untyped 'params' object, so the description adds significant value by listing each action's parameters, their locations (path vs query), and the allowed sort_by values. It stops short of explaining parameter meaning or defaults, but it compensates for the generic schema.

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?

The description states a specific resource ('Recipes other users published') and enumerates the three read operations, distinguishing this tool from AccountRecipesWriteTool by scoping it to reading published recipes. An agent can immediately tell what the tool does without opening the 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?

The description gives clear context for each action, e.g. searchRecipes for searching and getRecipe for reading installation details. It does not explicitly say when to avoid this tool or name the write sibling as an alternative, but the read-only scope is unambiguous.

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