Skip to main content
Glama
bruhsb
by bruhsb

paperclip_create_agent

Create a new agent directly in your company board without approval flow. Specify name, role, skills, and permissions to provision the agent instantly.

Instructions

⚠ Board-only: Directly create an agent; prefer paperclip_create_agent_hire for approval-flow hires.

Args:

  • companyId: string — Company UUID (required)

  • name: string — Display name (required, min 1 char)

  • role: enum (optional) — ceo|cto|cmo|cfo|engineer|designer|pm|qa|devops|researcher|general

  • title: string|null (optional) — Job title

  • icon: enum (optional) — UI icon identifier

  • reportsTo: UUID|null (optional) — Parent agent UUID

  • capabilities: string|null (optional) — Free-text capability description

  • desiredSkills: string[] (optional) — Skills to install at creation

  • adapterType: enum (optional) — process|http|claude_local|codex_local|…

  • adapterConfig / runtimeConfig: object (optional) — Adapter/runtime settings

  • budgetMonthlyCents: int ≥0 (optional) — Monthly spend cap in cents

  • permissions.canCreateAgents: boolean (optional) — CEO-level create permission

  • metadata: object|null (optional) — Arbitrary key-value metadata

Returns: Returns the created agent object with all fields.

Examples:

  • Use when: provisioning a new agent directly as a board user (bypasses approval flow)

  • Don't use when: you are an agent hiring a specialist — use paperclip_create_agent_hire instead

Error Handling:

  • 400: validation failure → check name is non-empty and enum values are valid

  • 401: authentication failed → check PAPERCLIP_API_KEY

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesCompany UUID to create the agent in
nameYesAgent display name
roleNoAgent role (default: general)
titleNoJob title shown on the agent profile
iconNoIcon displayed for this agent in the Paperclip UI
reportsToNoUUID of the parent agent this agent reports to
capabilitiesNoFree-text description of what this agent can do
desiredSkillsNoSkill names to install on the agent at creation
adapterTypeNoAdapter type controlling how the agent process is launched (default: process)
adapterConfigNoAdapter-specific configuration passed at agent launch
runtimeConfigNoRuntime configuration (heartbeat, concurrency, etc.)
budgetMonthlyCentsNoMonthly budget cap in cents (0 = unlimited / subscription billing)
permissionsNoGovernance permissions granted to this agent
metadataNoArbitrary key-value metadata attached to the agent
Behavior4/5

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

Annotations already indicate non-destructive and non-open-world behavior. The description adds context such as requiring a board API key, detailing error codes (400, 401, 403), and specifying that it bypasses approval flow. No contradictions with annotations.

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 well-structured with clear sections (Args, Returns, Examples, Error Handling). It is front-loaded with the important warning about board-only usage. While it is somewhat lengthy, each section serves a purpose and no information is redundant.

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?

Given the complexity (14 parameters, nested objects), the description covers parameter details, error scenarios, and usage context. There is no output schema, but the return object is described generically. The error handling and examples provide sufficient completeness.

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?

The input schema has 100% description coverage, so baseline is 3. The description adds value beyond the schema by explaining some parameters in more detail (e.g., permissions.canCreateAgents as CEO-level, icon as UI identifier). It also lists all parameters with types, but the schema already does that.

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 directly creates an agent and distinguishes it from the sibling tool paperclip_create_agent_hire, which handles approval-flow hires. The verb 'create' and resource 'agent' are specific, and the contrast is explicit.

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?

The description provides explicit usage guidance: it is for board-only direct hires, prefers the alternative sibling for approval flows, and includes 'Use when' and 'Don't use when' examples. Error handling also clarifies authentication and permission requirements.

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