Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_list_skills

List stored skills with optional status and limit filters. Use it to browse draft, tested, production, or deprecated skills before selecting one for reuse.

Instructions

List skills with optional filters

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoFilter by status: draft, tested, production, deprecated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.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 disclosure burden. It says nothing about read-only semantics, default ordering, pagination behavior, or what happens when filters match nothing — only the word "List" hints at a safe read, which is inference rather than disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five words is efficiently front-loaded with the verb and resource, so nothing is wasted. But the brevity comes at the cost of under-specification rather than being a tight, information-dense statement.

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?

With no annotations, no output schema, and half the parameters undocumented, the definition leaves significant gaps for an agent trying to call it correctly. At minimum it should clarify whether all skills are returned by default, how limit and status combine, and what the response contains.

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?

Schema description coverage is only 50%: status documents its allowed values inline, but limit has no description anywhere, so the agent cannot tell whether it is a page size, a cap on total results, or whether it interacts with pagination. The phrase "optional filters" adds nothing beyond what the schema already shows.

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?

"List skills with optional filters" gives a clear verb (list) and resource (skills), and implies it returns a collection rather than a single record, which differentiates it from reflex_get_skill in spirit. However, it never names or contrasts any sibling tool, and "optional filters" is too vague to pin down the tool's scope.

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 when-to-use guidance, no mention of when to prefer reflex_get_skill over this listing tool, and no note on prerequisites or result limits. The reader must infer everything about appropriate use from the five-word sentence.

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