Skip to main content
Glama
DynamicEndpoints

Advanced PocketBase MCP Server

get_record

Retrieve specific records from PocketBase databases by executing queries with defined parameters to access stored data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the get_record tool logic by fetching the record from PocketBase using collection.getOne(id). Dispatched from the main tool call handler.
    private async getRecord(collection: string, id: string) {
      if (!this.pb) {
        throw new Error('PocketBase not configured');
      }
    
      try {
        const record = await this.pb.collection(collection).getOne(id);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(record, null, 2)
            }
          ]
        };
      } catch (error: any) {
        throw new Error(`Failed to get record: ${error.message}`);
      }
    }
  • Input schema for get_record tool defining required 'collection' and 'id' string parameters.
      name: "get_record",
      description: "Get a specific record by ID",
      inputSchema: {
        type: "object",
        properties: {
          collection: {
            type: "string",
            description: "Collection name"
          },
          id: {
            type: "string",
            description: "Record ID"
          }
        },
        required: ["collection", "id"]
      }
    },
  • Inline tool registration and handler for get_record in the simple agent implementation, using Zod schema validation and PocketBase getOne.
      'get_record',
      {
        description: 'Get a specific record by ID',
        inputSchema: {
          collection: z.string().describe('Collection name'),
          id: z.string().describe('Record ID')
        }
      },
      async ({ collection, id }) => {
        await this.ensureInitialized();
        if (!this.pb) {
          throw new Error('PocketBase not initialized');
        }
    
        try {
          const record = await this.pb.collection(collection).getOne(id);
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(record, null, 2)
            }]
          };
        } catch (error: any) {
          throw new Error(`Failed to get record: ${error.message}`);
        }
      }
    );
  • Tool handler for get_record in Cloudflare agent, supports optional expand parameter for relations.
    this.server.tool(
      "get_record",
      "Get a specific record by ID",
      {
        collection: z.string().describe('Collection name'),
        id: z.string().describe('Record ID'),
        expand: z.string().optional().describe('Relations to expand')
      },
      async ({ collection, id, expand }) => {
        if (!this.pb) {
          throw new Error('PocketBase not initialized');
        }
    
        const record = await this.pb.collection(collection).getOne(id, { expand });
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(record, null, 2)
          }]
        };
      }
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

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

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