Skip to main content
Glama

list_intents

Read-only

Lists available intent plans and their human approval requirements for the active profile in the MCP memory gateway server.

Instructions

List available intent plans and whether each requires human approval in the active profile

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcpProfileNo
bundleIdNo
partnerProfileNo

Implementation Reference

  • The primary implementation of the `list_intents` tool logic, which processes policy bundles and profiles to return a list of available intents.
    function listIntents(options = {}) {
      const bundle = loadPolicyBundle(options.bundleId);
      const profile = assertKnownMcpProfile(options.mcpProfile || getActiveMcpProfile());
      const requiredRisks = getRequiredApprovalRisks(bundle, profile);
      const partnerStrategy = buildPartnerStrategy({
        partnerProfile: options.partnerProfile,
        tokenBudget: DEFAULT_TOKEN_BUDGET,
      });
    
      return {
        bundleId: bundle.bundleId,
        mcpProfile: profile,
        partnerProfile: partnerStrategy.profile,
        partnerStrategy: {
          verificationMode: partnerStrategy.verificationMode,
          recommendedChecks: partnerStrategy.recommendedChecks,
        },
        intents: bundle.intents.map((intent) => ({
          id: intent.id,
          description: intent.description,
          risk: intent.risk,
          actionCount: intent.actions.length,
          requiresApproval: requiredRisks.includes(intent.risk),
        })),
      };
    }
  • Registration of the `list_intents` tool in the tool registry.
    name: 'list_intents',
    description: 'List available intent plans and whether each requires human approval in the active profile',
    inputSchema: {
      type: 'object',
      properties: {
        mcpProfile: { type: 'string' },
        bundleId: { type: 'string' },
Behavior3/5

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

The annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds useful context about what information is returned (intent plans and their approval requirements) and the scope ('active profile'), but doesn't disclose behavioral details like pagination, rate limits, or authentication needs. No contradiction with annotations exists.

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 a single, efficient sentence that front-loads the core functionality. Every word contributes to understanding the tool's purpose without unnecessary elaboration or redundancy.

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?

Given the read-only annotation and lack of output schema, the description adequately covers the basic operation but leaves gaps. It doesn't explain the return format, how to interpret the approval status, or how parameters influence results. For a tool with undocumented parameters and no output schema, more detail would be helpful.

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

Parameters2/5

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

With 0% schema description coverage and 3 parameters (mcpProfile, bundleId, partnerProfile), the description provides no information about these parameters. It doesn't explain what they mean, when to use them, or how they affect the listing. The description fails to compensate for the lack of schema documentation.

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?

The description clearly states the tool's purpose: listing intent plans and their human approval requirements. It specifies the resource ('intent plans') and scope ('in the active profile'), but doesn't explicitly differentiate from sibling tools like 'plan_intent' or 'describe_semantic_entity' that might involve intents differently.

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?

No guidance is provided about when to use this tool versus alternatives. While the description implies this is for listing intents with approval status, it doesn't mention when to choose this over other intent-related tools like 'plan_intent' or 'describe_semantic_entity', nor does it specify prerequisites or exclusions.

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/IgorGanapolsky/mcp-memory-gateway'

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