Skip to main content
Glama
Sign In
Wick

Wick

by buildepicshit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

tool_catalog

Lists all active Wick tools grouped by assignment. Use to discover what functionality is available in the current process.

Instructions

Returns every known Wick tool with its group assignment and whether it is active in this process. Use to discover available functionality.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

The description implies a read-only operation returning data, which is adequate but could be more specific about scope (e.g., 'all tools' vs 'user-visible'). No annotations are provided, so the description carries the full burden, but it does not disclose potential side effects or performance characteristics.

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?

Two sentences, both front-loaded: first defines output, second states purpose. No wasted words or redundancy.

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?

For a parameterless catalog tool without output schema, the description fully conveys the return content and usage intent. It is complete given the tool's simplicity.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description does not need to add parameter information, and it does not.

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 clearly states the tool returns 'every known Wick tool with its group assignment and whether it is active', using a specific verb and resource. It distinguishes from sibling tools like tool_groups by emphasizing 'every' and 'discover available functionality'.

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?

The second sentence explicitly says 'Use to discover available functionality', providing clear context for when to use this tool. It does not mention exclusions or alternatives, which are not critical given the tool's discovery nature.

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