Skip to main content
Glama
Sign In
Baasix MCP Server

Baasix MCP Server

by tspvivek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

baasix_list_permissions

List permissions with optional filtering, pagination, and sorting to manage access control in a Baasix backend. Retrieves permissions by criteria.

Instructions

List all permissions with optional filtering

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": "baasix_list_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sortNoSort field and direction (e.g., "collection:asc")
limitNoPermissions per page (default: 10)
filterNoFilter criteria

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention pagination behavior, default limits, sort semantics, or what the response structure looks like, even though the schema parameters suggest pagination and sorting exist.

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

Conciseness4/5

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

The description is very short and front-loaded with the core purpose. It earns a high score for being concise, though it sacrifices useful behavioral context for brevity.

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?

With no annotations, no output schema, a nested filter object, and multiple permission-related sibling tools, this description is too minimal to be fully actionable. The agent gets no information about return shape, filter syntax, pagination defaults, or how this tool differs from related read tools.

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 covers all four parameters with descriptions, so the baseline is 3. The description adds no additional meaning beyond saying 'optional filtering', which weakly overlaps with the filter parameter but does not explain its structure or allowed values.

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 and resource: 'list all permissions' with optional filtering. However, it does not differentiate this tool from the similarly named sibling 'baasix_get_permissions', which may be seen as overlapping in purpose.

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?

There is no explicit guidance on when to use this tool versus alternatives like baasix_get_permissions or baasix_get_permission. The optional filtering capability is mentioned but not expanded with examples or context, leaving the agent to infer use cases.

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

Deploy Server

Other Tools