Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_get_skill

Retrieve a specific skill by ID from the continual learning brain, enabling AI agents to access and reuse stored capabilities.

Instructions

Get a specific skill by ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "skill_id": "<skill_id>"
    },
    "name": "reflex_get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skill_idYesSkill ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about read-only semantics, behavior on a missing or malformed ID (the schema allows up to 1000 chars), permissions, or what a "skill" record contains. For a simple lookup this is low-risk, but the description adds essentially no behavioral context beyond the verb.

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 short sentence, front-loaded with the verb and resource, with no filler. It is arguably under-specified rather than padded, which is a different (and lesser) flaw.

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

Completeness3/5

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

For a one-parameter read tool with no output schema, the definition is minimally viable, but it leaves the return value unexplained and gives no hint about where valid skill IDs come from. A single added clause about the returned record or ID provenance would make it complete.

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 the single skill_id parameter is documented structurally, and the description mirrors the schema's meaning ("by ID") without adding format, source, or example values. Baseline 3 is appropriate when the schema already does the work.

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 specific verb and resource ("Get a specific skill") plus the selection key ("by ID"), which distinguishes it in spirit from reflex_list_skills. It stops short of naming any sibling explicitly, so differentiation is implied rather than stated.

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: nothing says to call this after reflex_list_skills to resolve an ID, or what to do when the ID is unknown. The agent must infer the retrieval workflow entirely from the tool name.

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