Skip to main content
Glama
mrwyndham

PocketBase MCP Server

list_auth_methods

Retrieve available authentication methods for a PocketBase collection to configure user login options and security settings.

Instructions

List all available authentication methods

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionNoCollection name (default: users)users

Implementation Reference

  • Input schema for the 'list_auth_methods' tool, defining an optional 'collection' parameter defaulting to 'users'. This is part of the tools array registered with the MCP server.
    {
      name: 'list_auth_methods',
      description: 'List all available authentication methods',
      inputSchema: {
        type: 'object',
        properties: {
          collection: {
            type: 'string',
            description: 'Collection name (default: users)',
            default: 'users'
          }
        }
      }
  • src/index.ts:665-666 (registration)
    The closing of the tools array passed to this.server.setTools, registering all tools including 'list_auth_methods' with the MCP server.
      ],
    }));
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose whether this is a read-only operation, what permissions are required, how results are formatted, or if there are rate limits. 'List all' implies completeness but lacks detail on pagination or filtering beyond the schema parameter.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple list operation, making it highly efficient.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is too sparse. It doesn't explain what 'authentication methods' entails, how results are returned, or any behavioral nuances. Given the context of sibling auth tools, more guidance on usage and output would improve completeness.

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 description coverage is 100%, so the schema already documents the single parameter 'collection' with its type, description, and default. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high coverage.

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 verb ('List') and resource ('authentication methods'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_collections' or 'list_records' beyond the resource name, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, context for listing auth methods, or comparison to related tools like 'authenticate_user' or 'get_collection' that might overlap in functionality.

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/mrwyndham/pocketbase-mcp'

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