Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_candidate_tree

Read-only

Report the path and state of a request's full candidate tree, built from canonical plus candidate overlay during host validation, to confirm whether the stage is ready.

Instructions

MANAGER READ: path and state of a request's full candidate tree.

The tree is built by the host validation stage (host_commands/host_sweep) from canonical plus the candidate overlay; ready means the stage finished.

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": {
      "request_id": "<request_id>"
    },
    "name": "aiworkhub_manager_candidate_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesId of the worker request whose host-stage candidate tree to report.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.12.98

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuine semantic context beyond them: provenance (built by host_commands/host_sweep from canonical plus candidate overlay) and the meaning of the 'ready' state. It does not say what is returned when the stage has not run or when the request_id is unknown, which is a minor remaining gap.

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?

Two short sentences with the resource front-loaded and the explanatory provenance trailing. No filler, though the all-caps 'MANAGER READ' tag is slightly awkward phrasing rather than informative structure.

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?

With an output schema present, return values need not be described, and annotations cover the safety profile; the description supplies what structured fields cannot, namely where the tree comes from and what 'ready' means. Complete enough for a single-parameter read tool.

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?

There is a single parameter at 100% schema description coverage ('Id of the worker request whose host-stage candidate tree to report'), so the schema fully carries parameter meaning. The description adds only the framing that the tree is the host-stage tree, not new syntax or constraints.

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: it reports the path and state of a request's full candidate tree. The subject is unambiguous and an agent knows exactly which artifact it receives, though it does not contrast itself with any sibling tool by name.

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?

The 'MANAGER READ' prefix plus 'path and state of a request's full candidate tree' implies usage: inspecting the manager-side view of a worker request's candidates. No explicit when-to-use, when-not-to-use, or alternative is named, so the agent must infer the trigger condition.

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