Skip to main content
Glama

approve_instinct

Approve an instinct for active use by setting its approved_by status to human, enabling persistent tool context across chat sessions.

Instructions

Approve an instinct for active use (sets approved_by to human)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesInstinct ID to approve

Implementation Reference

  • Handler implementation for the approve_instinct tool, which calls registry.approve.
    case 'approve_instinct': {
      const id = String(args?.['id'] ?? '');
      if (!id) return { content: [{ type: 'text', text: 'Error: id is required' }] };
      try {
        const instinct = await registry.approve(id);
        return { content: [{ type: 'text', text: JSON.stringify({ approved: id, confidence: instinct.confidence, active: instinct.active }, null, 2) }] };
      } catch (e) {
        return { content: [{ type: 'text', text: `Error: ${e instanceof Error ? e.message : String(e)}` }] };
      }
    }
  • Tool definition and schema registration for approve_instinct.
    {
      name: 'approve_instinct',
      description: 'Approve an instinct for active use (sets approved_by to human)',
      inputSchema: {
        type: 'object' as const,
        properties: {
          id: { type: 'string', description: 'Instinct ID to approve' },
        },
        required: ['id'],
      },
    },
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses specific side effect 'sets approved_by to human' which reveals the data mutation behavior. Does not mention reversibility or authorization requirements, but the field update disclosure is valuable behavioral context.

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 with high information density. Front-loaded action ('Approve an instinct') followed by purpose ('for active use') and technical detail (parenthetical side effect). Zero redundancy; every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Appropriate for tool complexity: 1 parameter with full schema coverage, no output schema. Description covers the action, activation state, and side effect. Could be improved by contrasting with reject_instinct explicitly, but sufficient for correct invocation.

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

Parameters3/5

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

Schema coverage is 100% ('Instinct ID to approve'), so baseline applies. Description mentions 'instinct' generally but doesn't add syntax details, validation rules, or format specifics for the 'id' parameter beyond what the schema provides.

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?

Specific verb 'Approve' + resource 'instinct' + scope 'for active use' clearly defines the action. The parenthetical '(sets approved_by to human)' distinguishes this from sibling store_instinct (creation) and reject_instinct (declination) by specifying the exact approval mechanism.

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

Usage Guidelines3/5

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

Provides implied context with 'for active use' suggesting when to invoke the tool, but lacks explicit guidance on when to choose this over reject_instinct or prerequisites for approval. No 'when-not-to-use' or alternative named.

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