Skip to main content
Glama
Sign In
paperclip-mcp

paperclip-mcp

by shanewiseman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Update agent budget

pc_patch_agents_by_agent_id_budgets

Update an agent's monthly budget by providing the agent ID and new budget amount in cents.

Instructions

Update agent budget

Paperclip operation: PATCH /api/agents/{agentId}/budgets. Authorization class: board_or_agent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "body": "<body>"
    },
    "name": "pc_patch_agents_by_agent_id_budgets"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
pathYes

Output Schema

NameRequiredDescriptionDefault
bodyYes
headersYes
encodingYes
status_codeYes
content_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already indicate non-readonly (readOnlyHint false) and non-destructive (destructiveHint false). The description adds the operation type (PATCH) and authorization class but does not disclose behavioral traits such as constraints on budgetMonthlyCents, side effects, response format, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (3 sentences) with a clear first sentence. However, it includes technical details (endpoint, auth class) that are arguably redundant with the input schema and annotations. It could be more informative without becoming verbose.

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

Completeness2/5

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

Given the tool has 2 parameters, nested objects, and an output schema, the description is incomplete. It does not explain the parameters, response structure, or how this tool relates to other budget tools (e.g., pc_patch_companies_by_company_id_budgets).

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

Parameters1/5

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

Schema description coverage is 0%, yet the description provides no parameter explanations. It does not clarify that agentId identifies the agent or that budgetMonthlyCents is in cents. The description adds no value beyond the schema structure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Update agent budget', clearly identifying the action and resource. The API endpoint and authorization class provide additional context. However, it does not explicitly differentiate from sibling tools like pc_patch_companies_by_company_id_budgets, though the per-agent scope is implied by the path.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., company-level budget tools). Does not mention prerequisites, contexts where it should or should not be used, or any exclusions.

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

Deploy Server

Other Tools