Skip to main content
Glama
bruhsb
by bruhsb

paperclip_update_agent_permissions

DestructiveIdempotent

Update an agent's permissions to assign tasks and create new agents. Requires both fields and board-level authentication.

Instructions

⚠ Board-only: Update an agent's governance permissions (canAssignTasks, canCreateAgents). Both fields required.

Args:

  • agentId: string — Agent UUID (example: "agt_abc123")

  • canAssignTasks: boolean — Allow this agent to assign tasks to other agents

  • canCreateAgents: boolean — Allow this agent to create new agents (reserved for CEO by governance policy)

Returns: Returns the updated permissions object: agentId, canAssignTasks, canCreateAgents.

Examples:

  • Use when: granting or revoking an agent's ability to assign tasks after a board decision

  • Don't use when: you need to update config fields — use paperclip_update_agent instead

Error Handling:

  • 400: both canAssignTasks and canCreateAgents are required → supply both even if one is unchanged

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: permission denied → this tool requires a board (human) API key

  • 404: agent not found → verify ID with paperclip_list_agents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdYesAgent UUID
canAssignTasksYesAllow this agent to assign tasks to other agents
canCreateAgentsYesAllow this agent to create new agents (reserved for CEO by governance policy)
Behavior5/5

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

Beyond annotations (destructiveHint=true, idempotentHint=true), the description adds board-only auth requirement, governance policy (CEO reserved field), and detailed error handling for 400, 401, 403, 404. No contradictions.

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?

Structured with clear sections (warning, args, returns, examples, errors). Front-loaded with purpose and board-only restriction. Every sentence adds value, no wasted words.

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?

Comprehensive for a permission update tool with no output schema: covers purpose, parameters, usage, error scenarios, return structure, and governance constraints. Fully equips an agent to invoke correctly.

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

Parameters5/5

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

Schema coverage is 100% but description adds extra context: example agent UUID, governance note for canCreateAgents, requirement that both fields are always needed even if unchanged. This significantly aids correct parameter usage.

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?

The description clearly states the tool updates an agent's governance permissions with specific fields (canAssignTasks, canCreateAgents). It distinguishes from the sibling paperclip_update_agent by noting that tool handles config fields.

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?

Provides explicit when to use (granting/revoking after board decision) and when not to (config field changes, referencing alternative tool). Also notes board-only access, guiding correct invocation.

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

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/bruhsb/paperclip-mcp'

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