Skip to main content
Glama
aidemd-mcp

aidemd-mcp/server

by aidemd-mcp
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

aide_brain

Retrieve orientation or configuration sections from the brain during a task. Includes status and instructions for missing or misconfigured setup.

Instructions

On-demand brain entry-point tool. Call this when you need to reach the brain mid-task — do NOT call it on every /aide boot. Boot-time brain precondition state is already reported by aide_info.brain.status; firing aide_brain at boot duplicates that work unnecessarily.

Optional kind parameter — closed two-value vocabulary: "orientation" (default) or "config".

  • "orientation" — returns the orientation section: a runtime briefing delivered when an agent reaches for the brain mid-task. Omitting kind is equivalent to passing "orientation".

  • "config" — returns the integration-specific wiring flow, used by /aide:brain config to walk through brain setup.

Install-time seed sections (playbookIndex, studyPlaybook, updatePlaybook, researchIndex) are NOT surfaced via this tool — agents reach those via the brain's read tool against the on-disk seed files.

Response shape: { status, instructions } — exactly two fields. No backend, no connector, no name, no kind.

status — mirrors the BrainState tagged union from buildBrainState. The four-state vocabulary: ok, no-brain-aide, no-mcp-entry, mcp-drift. Branch on status alone — no other discriminant is present.

instructions — always non-empty on every branch. Act on this field directly:

  • On ok: the verbatim bytes of the selected section from the host's .aide/config/brain.aide, byte-identical to what the user wrote between that section's markers. No trimming, no normalization, no ${...} substitution. The selected section takes over from here — the tool has no further role.

  • On no-brain-aide: fixed remediation prose directing the user to run npx @aidemd-mcp/server@latest init. Do not proceed as if the brain were available.

  • On no-mcp-entry: fixed remediation prose directing the user to run npx @aidemd-mcp/server@latest sync and restart Claude Code. Do not proceed as if the brain were available.

  • On mcp-drift: fixed remediation prose directing the user to run npx @aidemd-mcp/server@latest sync and restart Claude Code, explicitly forbidding the agent from patching .mcp.json itself.

Non-ok remediation prose is identical regardless of kind — the file is broken for both sections in the same way.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoWhich section of brain.aide to return. `"orientation"` (default when omitted) returns the runtime briefing for mid-task brain access. `"config"` returns the integration-specific wiring flow used by `/aide:brain config`.

Tool Definition Quality

A5/5.0
Behavior5/5

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

With no annotations, the description carries full burden. It thoroughly details the response shape, four status states, instructions for each, and data integrity guarantees (no trimming, no substitution). Also notes that non-ok remediation is identical regardless of kind.

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?

Well-structured with headings and bullet points. Every sentence adds value, and the main purpose is front-loaded. No wasted text.

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?

Tool has 1 optional param, no output schema, no annotations. Description fully covers purpose, usage, response, edge cases, and remediation. Nothing missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant context: explains the two enum values, default behavior, and what each returns. Also details the response shape and status behavior beyond parameter meaning.

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?

Description clearly states it is an on-demand brain entry-point tool for mid-task use, and distinguishes from sibling tools like aide_info by warning not to call at boot. It specifies the two optional kinds and their purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (mid-task) and when not to (boot), with an alternative given (aide_info.brain.status). Also explains the kind parameter choices and defaults.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aidemd-mcp/server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server