PineBill

Update project

update_project

Destructive

Update an existing project. Use list_projects to find the project ID first. Pass only the fields that need to change.

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": {
      "id": "<id>"
    },
    "name": "update_project"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Project ID to update (from list_projects)
`name`	No	New project name
`budget`	No	New budget amount
`status`	No	New project status
`endDate`	No	New end date (ISO string, null to clear)
`currency`	No	New currency code
`startDate`	No	New start date (ISO string)
`customerId`	No	New customer ID (null to unlink)
`description`	No	New description (null to clear)
`assignedToId`	No	New employee ID (null to unassign)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0

Behavior3/5

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

Adds meaningful behavioral context beyond annotations by implying PATCH-style partial updates, so unspecified fields are left intact. However, annotations declare destructiveHint=true and idempotentHint=false, and the description does not warn about destructive effects or explain that repeating the same call may not be a no-op.

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?

Three short sentences, front-loaded with the purpose and then the prerequisite and the update rule. No filler or redundancy.

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

Completeness3/5

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

Adequate for a mutation tool with a fully documented 10-parameter schema and no output schema. It lacks any statement of what happens on success or failure and does not surface the destructive/non-idempotent characteristics the annotations flag.

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 coverage is 100%, so the schema already documents all 10 parameters including null-to-clear semantics. The description adds the partial-update instruction, which is real value, but supplies no field-specific meaning beyond the schema.

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?

States a specific verb and resource ("Update an existing project") that is immediately distinguishable from the create/delete/fetch siblings. It does not explicitly contrast with those siblings, but the verb+resource pairing is unambiguous.

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

Usage Guidelines4/5

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

Gives concrete prerequisites ("Use list_projects to find the project ID first") and the partial-update rule ("Pass only the fields that need to change"). No exclusions or when-not guidance, but the workflow context is clear and actionable.

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

All PineBill tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?