Skip to main content
Glama

List Recipe Activity Nodes

list_recipe_activity_nodes
Read-onlyIdempotent

Page through node-level results for one recipe build activity.

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": {
      "activity_ref": "<activity_ref>"
    },
    "name": "list_recipe_activity_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
activity_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 only extra signal is "page through," which merely restates what the cursor parameter already implies. Nothing is said about ordering, page size, termination conditions, or what happens with an invalid or expired cursor.

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 or redundancy. It is efficient, though the terseness edges into under-specification rather than pure economy.

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?

Complexity is low (two parameters, one required) and an output schema exists, so return values need no explanation. Still missing is the disambiguation from sibling listing tools and any hint about pagination behavior, which matters for a tool whose entire purpose is paging.

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%, so the description must carry the burden for both parameters. It partially does: "for one recipe build activity" explains that activity_ref identifies a single activity, and "page through" explains cursor as a pagination token. It adds no format, constraint, or cursor-lifecycle detail beyond those bare mappings.

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?

"Page through node-level results for one recipe build activity" gives a verb (page through) and a resource (node-level results scoped to one activity), so the general shape is clear. However, "node-level results" is vague about what a node result actually is, and the description never distinguishes this from the very similar sibling list_recipe_build_nodes. An agent can guess the intent but cannot confidently separate it from adjacent listing tools.

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 when-not-to-use exclusion, and no named alternative among the many sibling listing tools. The agent must infer from the name alone that this is the activity-scoped variant rather than the build-scoped one.

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