Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_task_template_list

Read-only

Lists all available task templates in the repository-bound registry, including seven built-ins plus a language-neutral custom validation entry for any language.

Instructions

MANAGER READ: list the bounded repository-bound template registry.

The seven built-ins are followed by one extra custom_validation entry (language_neutral, validation_source="caller") for repositories in any language, e.g. C++ with MSBuild and CTest commands.

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_task_template_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 establish readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing the exact registry contents (seven built-ins plus one custom_validation entry) and that the registry is bounded and repository-bound, so the agent knows the result set is small and repo-scoped.

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?

Content is front-loaded with the core action and scope, and the second sentence explains the composition of the registry. The C++/MSBuild/CTest example and validation_source detail are slightly more implementation depth than a list tool needs, but nothing is truly wasted.

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 no parameters, an output schema present, and read-only annotations, the description supplies what is needed: scope, boundedness, and expected entry composition. Only an explicit pointer to the sibling 'show' and create-from-template tools 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?

The tool takes zero parameters, so per the baseline the schema carries no semantic load and the description has nothing to compensate for. No parameter-level claims are needed or missing.

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 (list) and a precisely scoped resource (bounded repository-bound template registry), which is far more informative than the name alone. It does not explicitly distinguish itself from siblings like aiworkhub_task_template_show or aiworkhub_task_create_from_template, so it falls short of a 5.

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 signals the intended audience and read-only nature, implying this is used to discover available templates before creating tasks. However, it never says when to use this versus aiworkhub_task_template_show for a single template, nor any prerequisites or exclusions.

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