Skip to main content
Glama
bruhsb
by bruhsb

paperclip_create_agent_hire

Create an agent hire request to trigger governance approval and onboarding flow. Provide agent name, role, job title, capabilities, or linked goal.

Instructions

Create an agent hire request, triggering the governance approval and onboarding flow.

Args:

  • name: string — Agent display name (example: "DevOps Agent")

  • role: string — Agent role identifier (example: "devops")

  • title: string (optional) — Job title

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

  • goalId: string (optional) — Goal UUID to link the hire

  • projectId: string (optional) — Project UUID to associate

Returns: Returns the created hire request object with a pending approval linked.

Examples:

  • Use when: CEO agent initiating a new specialist hire after board approves the proposal

  • Don't use when: you need a generic approval — use paperclip_create_approval with type:'hire_agent' for custom payloads

Error Handling:

  • 400: validation failure → ensure name and role are non-empty

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: only the CEO agent has canCreateAgents permission → verify agent governance config

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAgent display name
roleYesAgent role (e.g. engineer, cto)
titleNoJob title
capabilitiesNoFree-text capability description
goalIdNoGoal UUID to link the hire to
projectIdNoProject UUID to associate
Behavior5/5

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

Discloses governance flow, pending approval, error codes, and permission restrictions (only CEO agent). Annotations already indicate non-destructive, so description adds value.

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?

Well-structured with clear sections (Args, Returns, Examples, Error Handling). No unnecessary words; all sentences add value.

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?

Complete given no output schema: explains return object type, when to use, and error handling. Covers all key aspects.

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?

Schema description coverage is 100%, so baseline 3. Description adds example values and context but doesn't significantly expand beyond schema for optional params.

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?

Clear verb+resource: 'Create an agent hire request, triggering the governance approval and onboarding flow.' Distinguishes from siblings like paperclip_create_agent and paperclip_create_approval.

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?

Explicit 'Use when' and 'Don't use when' with alternative tool name and rationale: 'use paperclip_create_approval with type: hire_agent for custom payloads'.

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