Skip to main content
Glama

busabase

by com.busabase
OverviewDiscussionsAdmin

List, grant, or revoke a principal's access on a node

node_permission

List, grant, or revoke a principal's access on a node

Grants access to a named user or space INSIDE the workspace — this is not link sharing (see node_share). Requires manage on the node. Roles escalate: read < changeRequest < write < manage; changeRequest lets someone propose changes without being able to merge them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoAccess level to grant (grant only).
actionYesWhat to do. Choose this before the other arguments.
nodeIdYesNode to inspect or change.
playbookNoOptional. The playbook you are following, as `kind:nodeId[:key]` from playbooks_search (e.g. `prompt:nod_123:log-visit`). Recorded on the change request so the person can see which playbook produced it.
principalIdNoId of the user or space.
principalTypeNoWhether the grant targets a user or a whole space.
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / playbook
      Added value: +{
+  "description": "Optional. The playbook you are following, as `kind:nodeId[:key]` from playbooks_search (e.g. `prompt:nod_123:log-visit`). Recorded on the change request so the person can see which playbook produced it.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=false. The description adds important context: the operation mutates permissions, requires 'manage' permission, and differentiates from link sharing. It explains the role hierarchy and the meaning of 'changeRequest'. No contradiction with annotations, though it doesn't disclose potential side effects of revoking access beyond the annotation's non-destructive hint.

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 deliver the core purpose and key constraints. Additional sentences add essential usage guidance without fluff. The distinction from node_share and the permission requirement are front-loaded, making the description immediately actionable.

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

Completeness4/5

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

For a tool with 7 parameters and no output schema, the description covers the critical aspects: purpose, permission requirement, role semantics, and distinction from sibling. It doesn't detail every parameter's behavior (e.g., what happens when revoking a role) but the schema covers parameter descriptions, and the description gives enough operational context for correct use.

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?

Schema has 100% coverage, so baseline is 3. The description adds value by explaining the role escalation ('read < changeRequest < write < manage'), clarifying the action selection ('Choose this before the other arguments.'), and describing the playbook parameter's purpose and format. This goes beyond the schema's enum descriptions.

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?

States a specific verb and resource: 'List, grant, or revoke a principal's access on a node.' Clearly distinguishes from sibling tool node_share by explicitly saying 'this is not link sharing' and referencing the alternative. The role hierarchy is explained, making it unambiguous.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'Grants access to a named user or space INSIDE the workspace — this is not link sharing (see node_share).' Also gives the precondition: 'Requires manage on the node.' and describes role escalation, so an agent knows the correct context and alternatives.

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

All busabase toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources