Skip to main content
Glama

getCollections

Retrieve all collection schemas from the Directus CMS API using the Model Context Protocol. Simplify schema management by accessing structured data without manual configuration.

Instructions

Get all collection schemas from Directus

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNoAuthentication token (default from config)
urlNoDirectus API URL (default from config)

Implementation Reference

  • index.ts:248-265 (registration)
    Registration of the 'getCollections' tool in the ListTools response, including its name, description, and input schema definition.
    {
      name: "getCollections",
      description: "Get all collection schemas from Directus",
      inputSchema: {
        type: "object",
        properties: {
          url: { 
            type: "string", 
            description: "Directus API URL (default from config)"
          },
          token: { 
            type: "string", 
            description: "Authentication token (default from config)"
          }
        },
        required: []
      }
    },
  • Handler implementation for the 'getCollections' tool within the CallToolRequestHandler switch statement. Fetches all collections from the Directus API /collections endpoint using axios and returns the JSON response.
    case "getCollections": {
      const token = toolArgs.token || CONFIG.DIRECTUS_ACCESS_TOKEN;
      
      const response = await axios.get(
        `${url}/collections`,
        { headers: buildHeaders(token) }
      );
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }
        ]
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It states what the tool does but doesn't describe return format, pagination, error conditions, authentication requirements, rate limits, or whether this is a read-only operation. The agent must infer behavior from the tool name alone.

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 with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the core purpose immediately.

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 insufficiently complete. It doesn't explain what 'collection schemas' include, the response format, or how this differs from other metadata retrieval tools. The agent lacks necessary context to use this tool effectively alongside its siblings.

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%, with both parameters ('token' and 'url') well-documented in the schema. The description adds no additional parameter context beyond what the schema provides, so it meets the baseline for adequate but unenriched parameter 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 action ('Get') and target resource ('all collection schemas from Directus'), providing specific verb+resource pairing. However, it doesn't explicitly differentiate from sibling tools like 'getFields' or 'getRelations' that also retrieve metadata, leaving some ambiguity about scope boundaries.

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. It doesn't mention prerequisites (like authentication), compare with similar tools (e.g., 'getFields' for field-level metadata), or indicate appropriate contexts for retrieving collection schemas versus other data.

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/pixelsock/directus-mcp'

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