Skip to main content
Glama
bruhsb
by bruhsb

paperclip_create_approval

Create a board review approval request for hire, CEO strategy, or budget override. Returns pending approval with ID and status.

Instructions

Create a new approval request for board review.

Args:

  • type: enum — hire_agent | approve_ceo_strategy | budget_override_required

  • payload: object — Type-specific payload (e.g. for hire_agent: { name, role, capabilities })

  • requestedByAgentId: string (optional) — Override requester agent UUID (defaults to caller)

Returns: Returns the created approval object: id, type, status:'pending', payload, createdAt.

Examples:

  • Use when: submitting a hire request or budget override request for board review

  • Don't use when: you want to use the streamlined hire flow — use paperclip_create_agent_hire instead

Error Handling:

  • 400: validation failure → ensure type is a valid enum and payload matches the type schema

  • 401: authentication failed → check PAPERCLIP_API_KEY

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesApproval type: hire_agent | approve_ceo_strategy | budget_override_required
payloadYesType-specific payload object (required by the API)
requestedByAgentIdNoAgent UUID of the requester (defaults to caller)
Behavior4/5

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

Annotations already indicate destructiveHint=false and openWorldHint=false. The description adds behavioral details beyond these: it describes the return object structure (id, type, status:'pending', payload, createdAt), error handling for 400 and 401, and the optional override for requester. This enriches the agent's understanding of the tool's behavior.

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), making it easy to scan. However, it is somewhat verbose (e.g., repeating the enum in the description and the schema). It could be slightly more concise without losing essential information.

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?

Given the tool has 3 parameters, no output schema, and nested objects, the description covers all necessary aspects: purpose, usage guidelines, parameter semantics, return format, and error handling. It is complete and leaves no significant gaps for an agent to understand the tool.

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 description coverage is 100%, so baseline is 3. The description adds meaningful extra context: for the 'type' parameter, it lists enum values; for 'payload', it gives an example for hire_agent; for 'requestedByAgentId', it clarifies override and default behavior. This adds value beyond the schema 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?

The description clearly states the tool creates an approval request for board review, with a specific verb 'Create' and resource 'approval request'. It explicitly distinguishes from a sibling tool by advising to use 'paperclip_create_agent_hire' instead when doing a streamlined hire, satisfying the sibling differentiation criterion.

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 with an 'Examples' section that includes 'Use when' and 'Don't use when' directives, and directly names an alternative tool (paperclip_create_agent_hire). This gives clear context for when to use this tool vs. alternatives.

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