Skip to main content
Glama
openhoat

aik-mcp

by openhoat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list

Browse available rules, skills, workflows, and agents, and filter them by tag, text query, category, or project directory to find applicable knowledge.

Instructions

List available content items (rules, skills, workflows, agents)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by tag
queryNoFilter by text query in title/description
categoryNoFilter by content category
projectDirNoProject directory used to detect the stack and annotate items with applicability (applies-to).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / projectDir
      Added value: +{
+  "description": "Project directory used to detect the stack and annotate items with applicability (applies-to).",
+  "type": "string"
+}
  2. Addedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not say whether this is a read-only listing, how results are ordered or paginated, how multiple filters combine, or what 'available' means. Only the content-type enumeration adds useful context.

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?

A single, front-loaded sentence with zero filler; the tool's subject matter is communicated immediately without redundant restatement of the name.

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 four-parameter, multi-filter listing tool with no annotations and no output schema, the description leaves too much unsaid: result ordering, pagination, filter combination semantics, and the distinction from list_installed and search are all absent.

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 description coverage is 100%, so all four filter parameters are already documented in the schema, making 3 the baseline. The description adds no extra meaning about filter composition or defaults beyond what the schema states.

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 clear verb (List) and resource (content items) and enumerates the four content kinds it covers, which sharpens the otherwise generic name 'list'. It does not explicitly distinguish itself from siblings like list_installed or search, so an agent must infer the boundary.

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 use this tool versus the many siblings (search, get, list_installed). The reader is left to infer that this lists all content while search filters, and no preconditions or exclusions are given.

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