Skip to main content
Glama

Create project budget item

create_project_budget_item

Create a new project budget item. Requires project_budget_items:write scope.

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": {
      "project_id": "<project_id>",
      "category": "<category>"
    },
    "name": "create_project_budget_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoNotes
categoryYesBudget category (required)
project_idYesProject ID (required) - resolve via list_projects
descriptionNoDescription
actual_amountNoActual amount
planned_amountNoPlanned amount

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID (required)"New value: +"Project ID (required) - resolve via list_projects"
  2. Changed2 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "labor",
      -  "materials",
      -  "equipment",
      -  "subcontractors",
      -  "permits",
      -  "contingency",
      -  "other"
      -]New value: +[
      +  "lump_sum",
      +  "labor",
      +  "materials",
      +  "equipment",
      +  "subcontractors",
      +  "permits",
      +  "contingency",
      +  "other"
      +]
    • addedInput schema / properties / notes
      Added value: +{
      +  "description": "Notes",
      +  "maxLength": 5000,
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  4. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  5. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  6. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false), so the description need not repeat that. It does add genuinely useful auth context by naming the required project_budget_items:write scope, but says nothing about what a duplicate submission does (non-idempotent) or whether the created item is returned.

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?

Two short sentences, front-loaded with the action and with zero padding. It is efficient, though the brevity borders on under-specification rather than maximal usefulness.

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?

Annotations cover the safety profile and the schema is fully documented, so the core call is answerable. Still, for a create operation with no output schema, the description never says what comes back or how the new item's id is obtained, and it omits the project_id resolution step that the schema references.

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% and the schema itself carries useful hints, including 'resolve via list_projects' for project_id and the full category enum. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ('Create a new project budget item'), which is clearly distinguishable from the update_project_budget_item and delete_project_budget_item siblings. It does not, however, differentiate itself from other create_* budget-adjacent tools such as create_budget or create_cost_category beyond the resource name.

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 versus create_budget, bulk_create, or update_project_budget_item. The only added context is a permission scope, which is an authorization prerequisite rather than a routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources