Skip to main content
Glama

stats

Check overall health of the instinct store: total patterns, level distribution, category breakdown, and confidence metrics. Get instant overview without modifying data.

Instructions

Summary of the instinct store: totals, level distribution, category breakdown.

    Use for a quick health check — how many patterns exist, how they
    are distributed across promotion levels, which categories dominate,
    and the average/peak confidence. Read-only; no side effects; no
    params.

    For a time-ranged view of what's been observed recently use
    trending(days). For end-of-session snapshot that also runs
    consolidate use session_summary().

    Returns:
        {"total": int, "raw": int, "mature": int, "rules": int,
         "universal": int, "avg_confidence": float, "max_confidence": int,
         "by_category": {<category>: {"count": int,
                                      "avg_confidence": float}}}

        Level counts partition "total": raw + mature + rules +
        universal == total. "by_category" keys are a subset of
        ("sequence", "preference", "fix_pattern", "combo") — only
        categories actually present appear as keys. Empty store returns
        zero counts everywhere, not an error.
    

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?

Despite no annotations, the description is fully transparent: 'Read-only; no side effects; no params.' It also explains empty store behavior and return structure, leaving no hidden traits.

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 highly concise: a brief purpose statement, then usage guidelines, then a clear return spec. Every sentence earns its place without repetition or fluff.

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?

For a parameterless tool with an output schema, the description is complete: it covers all relevant aspects (purpose, usage, behavior, return details, edge cases), leaving no gaps.

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?

No parameters exist, so schema coverage is 100% trivially. The description adds value by detailing return fields and their relationships (e.g., level partition sums to total), which goes beyond the output schema alone.

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 'Summary of the instinct store' and lists specific metrics (totals, level distribution, category breakdown). It explicitly distinguishes from siblings by naming trending and session_summary as alternatives, fulfilling 'specific verb+resource, distinguishes from siblings'.

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 provides explicit usage guidance: 'Use for a quick health check' and states when to use trending or session_summary instead. This gives clear context and exclusion criteria.

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