Skip to main content
Glama

getPermissions

Retrieve permissions from Directus CMS API using a Node.js server. Input URL, token, and optional query parameters to manage access control efficiently.

Instructions

Get permissions from Directus

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoQuery parameters like filter, sort, limit, etc. (optional)
tokenNoAuthentication token (default from config)
urlNoDirectus API URL (default from config)

Implementation Reference

  • Handler implementation for the 'getPermissions' tool. It fetches permissions from the Directus '/permissions' endpoint using axios GET request with authentication token and optional query parameters, then returns the JSON response as text content.
    case "getPermissions": {
      const token = toolArgs.token || CONFIG.DIRECTUS_ACCESS_TOKEN;
      const query = toolArgs.query as Record<string, any> | undefined;
      
      const response = await axios.get(
        `${url}/permissions`,
        { 
          headers: buildHeaders(token),
          params: query
        }
      );
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }
        ]
      };
    }
  • index.ts:480-501 (registration)
    Registration of the 'getPermissions' tool in the listTools response, including its name, description, and input schema definition.
    {
      name: "getPermissions",
      description: "Get permissions 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)"
          },
          query: {
            type: "object",
            description: "Query parameters like filter, sort, limit, etc. (optional)"
          }
        },
        required: []
      }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It doesn't mention whether this is a read-only operation, what authentication is required beyond the optional token parameter, potential rate limits, or what format the permissions data returns. For a tool with 3 parameters and no annotation coverage, this is insufficient.

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 gets straight to the point without unnecessary elaboration.

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 3 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what permissions are in the Directus context, what data structure to expect, or how the query parameter should be structured despite its complexity (object type). The description fails to compensate for the lack of structured metadata.

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?

The schema description coverage is 100%, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema (query parameters, authentication token, API URL). This meets the baseline expectation when schema coverage is complete.

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 ('Get') and resource ('permissions from Directus'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'getRoles' or 'getUsers' that also retrieve different types of Directus data, preventing 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. With sibling tools like 'getRoles' and 'getUsers' that retrieve related data, there's no indication of what distinguishes permissions from these other entities or when an agent should choose one over another.

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