Skip to main content
Glama
glachana

bcquality-mcp

by glachana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List BCQuality skills

bcquality_list_skills
Read-onlyIdempotent

List available BCQuality skills, filtering by layer or kind to locate the rules and adapters you need.

Instructions

Lists all skills (meta-skills under /skills/, host-skill adapters at skills//SKILL.md, and action skills under /skills/). Filter by layer or kind (action-skill | host-skill | meta).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
layerNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "action-skill",
-  "meta"
-]New value: +[
+  "action-skill",
+  "host-skill",
+  "meta"
+]
  2. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

The description adds context beyond the readOnlyHint and idempotentHint: it lists the exact skill locations and the filter dimensions. It does not disclose default behavior when no filters are supplied (though 'all skills' implies a full listing), how the two filters interact when combined, or whether sorting/pagination exists.

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: the first states the general result and scope, the second lists the filter options. There is no redundant phrasing, and the key purpose is front-loaded.

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?

The tool is a simple list with optional filters and already has outputSchema and safety annotations. The description covers what is returned (skills of any of the listed kinds), the primary filter dimensions, and where those skills are located. The main remaining ambiguity is whether the layer filter applies only to action skills or to all categories, but the overall context is complete enough for selection and invocation.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It maps kind values to the skill categories, explains that action skills are tied to a layer, and the phrase 'filter by layer or kind' clarifies both are optional narrowing axes. The description stops short of explaining how layer values map to filter scope, but it adds genuine semantic value.

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 starts with a clear verb+resource ('Lists all skills') and gives a specific breakdown of what counts as a skill: meta-skills, host-skill adapters, and action skills. This distinguishes it from sibling list tools (list_domains, list_knowledge) and the more specific get_skill tool.

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?

It tells the agent when the tool is relevant (to list all skills) and that filtering by layer or kind is possible. However, it does not name alternatives or give exclusion criteria such as 'use get_skill to retrieve a single skill' or 'use search_knowledge when a full enumeration is not needed.'

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