Skip to main content
Glama

list_instincts

Retrieve all active instincts with confidence scores to understand available contextual rules and preferences in the MCP Context Provider system.

Instructions

List all loaded instincts with their confidence scores

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the `list_instincts` tool, which retrieves all instincts from the engine and returns them as a JSON-formatted list.
    case 'list_instincts': {
      const instincts = engine.getAllInstincts().map((i) => ({
        id: i.id,
        domain: i.domain,
        rule: i.rule,
        confidence: i.confidence,
        active: i.active,
        approved_by: i.approved_by,
        usage_count: i.usage_count,
      }));
      return { content: [{ type: 'text', text: JSON.stringify(instincts, null, 2) }] };
    }
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. While it specifies 'loaded' (state constraint) and 'confidence scores' (returned data), it omits safety profile (read-only?), pagination behavior, or what occurs when no instincts are loaded.

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?

Single sentence, front-loaded with verb, zero redundancy. Every word serves a purpose: scope ('all'), state ('loaded'), resource ('instincts'), and return detail ('confidence scores').

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 zero-parameter tool without output schema, the description minimally suffices by mentioning the key return value (confidence scores). However, it lacks output structure details, field descriptions beyond scores, or error conditions that would aid invocation.

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?

Zero parameters present, establishing baseline 4. Schema coverage is 100% (trivially), and description correctly implies no filtering or configuration is possible for this operation.

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?

Clear verb 'List' with specific resource 'loaded instincts' and data attribute 'confidence scores'. Distinguishes from sibling management tools (store_instinct, approve_instinct) by specifying 'loaded' state, though it doesn't explicitly contrast with list_available_contexts.

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?

Provides no guidance on when to use versus siblings like store_instinct or get_tool_context. No mention of prerequisites, sequencing, or selection criteria for when listing is appropriate.

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/doobidoo/MCP-Context-Provider'

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