Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_recipe_list

Read-only

Lists persisted recipes with their identity, digest, purpose, risk, capabilities and parameter signature, excluding argv templates. Supports limit and offset paging, so you can survey the recipe registry before running any task.

Instructions

MANAGER READ: bounded identity/contract listing of persisted recipes.

Returns each manifest's identity, digest, purpose, risk, capabilities and parameter signature -- never its argv template. An empty store is a legitimate repository state and returns registry_count zero.

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": "aiworkhub_manager_recipe_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum recipes to return; default 100, clamped to 1-1000.
offsetNoNumber of recipes to skip before the first one returned, for paging; default 0.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / limit / description
      Added value: +"Maximum recipes to return; default 100, clamped to 1-1000."
    • addedInput schema / properties / offset / description
      Added value: +"Number of recipes to skip before the first one returned, for paging; default 0."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), so the bar is lower, and the description still adds real value: it discloses the security-relevant fact that argv templates are never returned, and that an empty store returns registry_count zero. It does not discuss pagination behavior or ordering, which is a minor gap.

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?

Two short sentences, front-loaded with the READ scope and the resource, then the return-content contract and the empty-state caveat. Every sentence earns its place 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?

An output schema exists, so return-value detail is unnecessary, and the description still summarizes the returned fields and the empty-store shape. The remaining omission is paging guidance, which the schema already covers.

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 coverage is 100% with both limit and offset fully documented in the schema, including defaults and clamping, so the baseline is 3. The description adds no further parameter semantics beyond its "bounded" framing.

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+resource ("listing of persisted recipes") with the qualifier "bounded identity/contract" and clarifies exactly what fields are returned (identity, digest, purpose, risk, capabilities, parameter signature). It distinguishes itself from write/single-item siblings implicitly via "list", but never names recipe_show or recipe_run explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the tool is a listing, and the empty-store note signals that zero results are a valid outcome rather than an error. There is no explicit when-to-use vs recipe_show or recipe_run, nor any stated precondition for invoking it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools