Skip to main content
Glama

export_rules

Export promoted behavioral patterns as structured JSON for programmatic use in analytics or external systems. Filters to high-confidence rules.

Instructions

Export promoted-level patterns (rule + universal) as structured JSON.

    Filters to patterns with promoted >= 2 — the threshold set by
    consolidate() after enough reinforcement. Intended for programmatic
    consumption: analytics pipelines, sibling agents, external
    dashboards. Read-only; takes no parameters.

    For human-readable Markdown use export_claude_md(). For platform-
    specific formats use export_platform() (.cursorrules, .windsurf,
    AGENTS.md) or export_skill() (anthropics/skills SKILL.md). For
    lower-confidence audits use list_instincts(min_confidence=5).

    Returns:
        {"rules": [<record>, ...], "count": int, "hint": str}

        Each <record> has: "pattern" (str key with prefix),
        "category" ("sequence"|"preference"|"fix_pattern"|"combo"),
        "confidence" (int observation count),
        "promoted" (2=rule, 3=universal — lower levels are filtered out),
        "level" ("rule"|"universal"),
        "project" (str fingerprint, "" = global),
        "source" (str origin tag), "metadata" (parsed dict),
        "explain" (str human note),
        "first_seen" and "last_seen" (ISO 8601 timestamps).

        Sorted by promoted descending, then confidence descending.
        Empty "rules" means no pattern has reached rule level yet —
        the "hint" directs to run consolidate() first, then retry.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description declares the tool as read-only and takes no parameters, which is a key behavioral trait. It also details the return format, including the structure of each record and the meaning of an empty 'rules' array. With no annotations provided, the description fully covers the behavioral aspects.

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?

The description is well-structured with a clear main statement, then usage guidelines, then return format in a bulleted list. Every sentence provides unique value, and the information is front-loaded. Despite its length, it remains focused and efficient.

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 that the tool has no parameters, no annotations, but has a detailed output schema provided in the description, the description is fully complete. It covers purpose, usage, return format, and edge cases (empty results), leaving no gaps for an AI agent to misunderstand.

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?

There are zero parameters, and the schema description coverage is 100% (since no params exist). The description adds context by stating that the tool takes no parameters, which is sufficient. According to guidelines, baseline for 0 parameters is 4.

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's action ('Export'), the resource ('promoted-level patterns (rule + universal)'), and includes a specific threshold (promoted >= 2). It also differentiates from sibling tools by naming alternatives like export_claude_md, export_platform, export_skill, and list_instincts.

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?

The description explicitly states when to use this tool ('for programmatic consumption: analytics pipelines, sibling agents, external dashboards') and provides clear alternatives for other use cases (human-readable Markdown, platform-specific formats, lower-confidence audits). It also notes that if no patterns have reached rule level, the hint directs to run consolidate() first.

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