Skip to main content
Glama

Read a Recipe Capability

get_recipe_capability
Read-onlyIdempotent

Read the complete contract for one supported recipe node type.

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": {
      "node_type": "<node_type>"
    },
    "name": "get_recipe_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.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, openWorldHint=false and destructiveHint=false, so safety and idempotency are covered structurally. The description adds only that the returned contract is "complete," and says nothing about behavior for an unsupported node_type (error vs empty result), which matters given openWorldHint=false implies a closed set of valid types.

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?

A single front-loaded sentence with no filler, well matched to a one-parameter read tool. It is efficient but arguably too terse, since a second short clause about valid node types or prerequisites would earn its place.

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

Completeness3/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-value structure need not be described. However, for a tool whose only parameter has zero schema documentation and whose valid values are a closed set, the description should state how to obtain valid node types and what happens on an invalid one; that gap keeps it at minimum-viable completeness.

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 description coverage is 0% for the single node_type parameter, so the description must compensate. "One supported recipe node type" does convey that the value must be a recognized type rather than free text, but it never gives the expected format or points to where valid values are enumerated, leaving the agent to guess.

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: "Read the complete contract for one supported recipe node type." An agent can tell this returns a capability/contract document rather than a build plan or model, distinguishing it from siblings like get_recipe_acceptance_plan or get_recipe_model, though it never names those siblings explicitly.

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 and no reference to list_recipe_capability_types, which presumably is how an agent discovers valid node types before calling this. The phrase "one supported recipe node type" hints at a prerequisite but never states it or names the alternative tool.

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