Skip to main content
Glama

refresh_task_catalog

Synchronize official task documentation with reviewed schemas and report differences, optionally forcing a refresh to keep task definitions current.

Instructions

Synchronize official task documentation and report differences from reviewed schemas.

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

Input Schema

NameRequiredDescriptionDefault
forceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. "Synchronize" implies a state-changing operation, but the description never says what gets overwritten, whether local schemas are replaced, whether network access or elevated permissions are needed, or how the reported differences are surfaced. An output schema exists, so return shape is covered, but the mutation/safety profile is not.

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?

One compact sentence with the primary action front-loaded and no filler. It is efficient, though brevity here comes at the cost of the missing details noted elsewhere.

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

Completeness2/5

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

For a synchronization tool with zero annotation coverage and an undocumented flag that plausibly changes destructive behavior, the definition is too thin. The presence of an output schema excuses it from describing return values, but it still needs to explain what is synchronized and what `force` does.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter `force` has 0% schema description coverage, and the description never mentions it. Whether `force` bypasses a diff confirmation, overwrites unreviewed changes, or triggers a full re-fetch is unknown, and that is exactly the meaning an agent needs before setting it to true.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ("Synchronize") with a resource ("official task documentation") and adds a secondary effect ("report differences from reviewed schemas"). However, "official task documentation" and "reviewed schemas" are left undefined, so an agent cannot tell exactly what is being refreshed (local cache, remote catalog, schema registry) or how this differs from siblings like get_docs or get_task_schema.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives (get_docs, get_task_schema), no prerequisites, and no exclusions. The only implied guidance comes from the tool name, not the description text.

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