Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_recipe_show

Read-only

Retrieve a persisted recipe's exact canonical manifest by recipe ID, optionally selecting a version; omit version to get the highest stored version with a verifiable digest.

Instructions

MANAGER READ: one persisted recipe in its exact canonical manifest form.

With version omitted the highest stored version wins, ordered by the registry's own version key. The returned manifest is exactly the payload the recipe digest hashes, so the reported digest is independently checkable.

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": {
      "recipe_id": "<recipe_id>"
    },
    "name": "aiworkhub_manager_recipe_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoRecipe version to show, as listed by aiworkhub_manager_recipe_list; omit for the highest stored version.
recipe_idYesId of a persisted recipe, as listed by aiworkhub_manager_recipe_list.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / recipe_id / description
      Added value: +"Id of a persisted recipe, as listed by aiworkhub_manager_recipe_list."
    • addedInput schema / properties / version / description
      Added value: +"Recipe version to show, as listed by aiworkhub_manager_recipe_list; omit for the highest stored version."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds meaningful context: the manifest is exactly what the digest hashes, making verification possible. It stops short of describing failure behavior when a recipe or version is missing, but it adds more than the annotations alone.

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 brief, front-loaded with the read scope, and every sentence adds specific information about version defaulting or manifest/digest exactness.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, full schema coverage, annotations covering safety, and an output schema present, the description provides enough additional context about the returned manifest and digest relationship. Nothing essential for correct invocation is missing.

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?

Schema coverage is 100%, so both parameters are already documented. The description adds useful semantics for the version parameter by stating that omission selects the highest stored version according to the registry's own version key, which goes beyond the schema text.

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 read operation on a single persisted recipe and specifies that it returns the exact canonical manifest form. This distinguishes it from sibling operations such as recipe_list, recipe_register, and recipe_run without requiring the schema to be opened.

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?

It clearly explains the version-selection behavior and implies the tool is for inspecting one recipe's canonical manifest. It does not explicitly name alternatives like recipe_list or recipe_run, so the guidance is strong but not complete for when-to-use-vs-alternative decisions.

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