Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_task_template_show

Read-only

Shows a single task template by exact short name or full ID, rejecting any unrecognized ID to prevent mismatches.

Instructions

MANAGER READ: show one exact short or full template ID, fail closed.

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": {
      "template_id": "<template_id>"
    },
    "name": "aiworkhub_task_template_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYesExact short template name, or the current full id (ending in the definition digest), as listed by aiworkhub_task_template_list; anything else is refused.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.67
    • addedInput schema / properties / template_id / description
      Added value: +"Exact short template name, or the current full id (ending in the definition digest), as listed by aiworkhub_task_template_list; anything else is refused."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add one genuinely useful behavioral fact — 'fail closed', i.e. a non-matching ID is refused rather than resolved loosely — but says nothing about permissions, lookup cost, or error shape.

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?

A single compact sentence with the action front-loaded and no redundant clauses. Slightly terse to the point of abbreviation ('MANAGER READ', 'fail closed' both require the schema for full meaning).

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?

One required parameter and an output schema mean the description needn't explain return values; it covers what the tool does and its strict-input behavior. The only real gap is not routing the agent to the list tool for discovery.

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%, and the schema's template_id description is richer than the tool description (it names the list tool as the source and the refusal behavior). The description's mention of 'short or full template ID' restates what the schema already documents, so baseline 3 applies.

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 concrete verb and resource: show one template, identified by either a short name or a full digest-bearing ID. 'one exact' differentiates it implicitly from the plural listing sibling aiworkhub_task_template_list, though it never names that sibling.

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 implied by 'MANAGER READ' and the single-ID scope, but the description never states when to call this versus aiworkhub_task_template_list, nor that the ID must first be obtained from that list (that prerequisite lives only in the schema text).

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