Skip to main content
Glama

List Recipe Activity Assertions

list_recipe_activity_assertions
Read-onlyIdempotent

Page through assertion results for one recipe acceptance 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_assertions"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
activity_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's one addition is the pagination behavior ('Page through'), which is genuinely beyond the annotations, but it says nothing about ordering, page size limits, or what an assertion record contains.

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 front-loaded sentence with no filler. The scope constraint and the pagination nature are both stated immediately, and nothing is wasted.

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 values need not be explained, and the annotations cover safety. But for a tool with 0% schema description coverage on two parameters and a large sibling surface, the description does not say enough about parameter provenance or how this listing differs from adjacent listing tools.

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 carries the full burden for both parameters; it does implicitly map 'one recipe acceptance activity' to activity_ref and 'Page through' to cursor, which is meaningful compensation. However, it gives no format, provenance, or validity expectations for activity_ref (a 4096-char string) or cursor semantics such as where a cursor comes from.

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 pairs a specific verb ('Page through') with a specific resource ('assertion results') and scopes it to 'one recipe acceptance activity,' which separates it conceptually from siblings such as list_recipe_activity_nodes. It stops short of explicitly naming a sibling or contrasting scope, so it is clear but not maximally differentiating.

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 statement of when to use this tool versus the many sibling listing tools (nodes, runs, builds), and no mention of prerequisites such as needing an activity_ref obtained from another call. The only implicit cue is 'Page through,' which hints at pagination but gives no when-not guidance.

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