Skip to main content
Glama
DynamicEndpoints

pocketbase-mcp-server

smithery_discovery

Explore and analyze PocketBase database structures using Discovery to uncover schema details, relationships, and metadata for enhanced data management and optimization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'smithery_discovery' tool, returning static JSON with server capabilities and status for fast tool discovery.
      async () => {
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({
              server: 'pocketbase-mcp-server',
              version: '0.1.0',
              capabilities: ['pocketbase', 'database', 'realtime', 'auth', 'files'],
              status: 'ready',
              tools: ['health_check', 'list_collections', 'create_record', 'query_records'],
              discoveryTime: '0ms'
            }, null, 2)
          }]
        };
      }
    );
  • Registration of the 'smithery_discovery' tool including empty input schema and handler function.
    this.server.tool(
      "smithery_discovery",
      "Fast discovery endpoint for Smithery tool scanning",
      {},
      async () => {
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({
              server: 'pocketbase-mcp-server',
              version: '0.1.0',
              capabilities: ['pocketbase', 'database', 'realtime', 'auth', 'files'],
              status: 'ready',
              tools: ['health_check', 'list_collections', 'create_record', 'query_records'],
              discoveryTime: '0ms'
            }, null, 2)
          }]
        };
      }
    );
  • Handler function for the 'smithery_discovery' tool in the simple agent implementation.
      async () => {
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({
              server: 'pocketbase-mcp-server',
              version: '0.1.0',
              capabilities: ['pocketbase', 'database', 'realtime', 'auth'],
              status: 'ready',
              discoveryTime: '0ms'
            }, null, 2)
          }]
        };
      }
    );
  • Handler case for 'smithery_discovery' in the Cloudflare Worker execution switch statement.
    case 'smithery_discovery':
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            server: 'pocketbase-mcp-server',
            version: '0.1.0',
            capabilities: ['pocketbase', 'database', 'realtime', 'auth', 'files', 'stripe', 'email'],
            status: 'ready',
            discoveryTime: '0ms',
            environment: 'cloudflare-worker',
            totalTools: 14
          }, null, 2)
        }]
      };
  • Schema definition for 'smithery_discovery' tool in the tools/list response.
      name: 'smithery_discovery',
      description: 'Fast discovery endpoint for Smithery tool scanning',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/DynamicEndpoints/pocketbase-mcp-server'

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