Skip to main content
Glama

import_claude_md

Parse a CLAUDE.md file and ingest backtick-wrapped patterns into an instinct store. Bootstraps or syncs behavioral rules from an existing project.

Instructions

Parse a CLAUDE.md file and ingest its backtick-wrapped patterns.

    Scans the file for patterns matching the instinct convention
    (seq:..., pref:..., fix:..., combo:...) and imports each as an
    observation. Extracts confidence counts and explain text when
    present on the line.

    Use this to bootstrap a fresh instinct store from an existing
    project's CLAUDE.md, or to sync rules authored by hand.

    Args:
        source: Path to the CLAUDE.md file. Read-only — the source
            file is not modified.

    Returns:
        Dict with keys: "imported" (int — new patterns), "merged"
        (int — reinforced existing patterns), "skipped" (int — lines
        that looked pattern-like but failed validation), "source" (str).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses read-only nature ('the source file is not modified'), extraction details (confidence counts, explain text), and return dict keys. No annotations present, so description carries full burden and does well.

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?

Description is concise with a clear head sentence and detailed follow-up. Could be slightly more front-loaded, but no unnecessary sentences.

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?

Given a simple tool with one parameter, no annotations, and an output schema, the description thoroughly covers purpose, usage, behavior, and return values. Complete for the context.

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?

Single parameter 'source' has 0% schema description coverage. Description adds 'Path to the CLAUDE.md file', providing essential meaning. Minimal but adequate for a simple string path.

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 clearly states the tool parses a CLAUDE.md file and ingests backtick-wrapped patterns, with a specific verb and resource. It distinguishes itself from siblings like export_claude_md and inject_claude_md.

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

Usage Guidelines4/5

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

Explicitly states when to use (bootstrap or sync rules). Does not mention alternatives or when not to use, but context from siblings provides differentiation.

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/WRG-11/instinct'

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