pocketbase-mcp

Get collection scaffolds

get_collection_scaffolds

Retrieve default collection templates for base, auth, and view types to use as a starting point before creating a collection. Copy, customize fields, and create.

Instructions

Return default collection templates (scaffolds) for each collection type (base, auth, view). Useful as a starting point before calling create_collection — copy a scaffold, adjust the name and fields, then create it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_collection_scaffolds"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are present, so the description carries the behavioral burden. It states the read-only nature ('Return default collection templates') and the intended workflow with create_collection, which is sufficient for a zero-parameter read tool. It does not disclose output shape, but no output schema exists; the core behavior and side-effect-free nature are clear.

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?

Two sentences, front-loaded with the action, and every clause earns its place. The workflow guidance (copy, adjust, create) is useful without adding bulk.

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

Completeness5/5

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

For a tool with no parameters, no annotations, and no output schema, the description is complete: it defines what is returned, enumerates the result categories, and explains how the result should be used with create_collection. Nothing needed to invoke it correctly is missing.

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

Parameters4/5

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

The input schema has zero properties and coverage is 100%, so there are no parameters whose meaning needs explaining. The description adds value by naming the three scaffold categories in the output, aligning with the 0-parameter baseline.

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?

Description begins with a specific verb and object: 'Return default collection templates (scaffolds)' and enumerates the exact collection types (base, auth, view). This clearly separates it from siblings like get_collection or list_collections, which operate on existing collections, and ties it to create_collection.

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

Usage Guidelines4/5

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

It gives an explicit when-to-use signal: 'Useful as a starting point before calling create_collection' and describes the copy-adjust-create workflow. It does not explicitly list when-not-to-use or name an alternative tool, but the context is clear enough for the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server