Skip to main content
Glama

Project budgets

project_budgets
Read-onlyIdempotent

Budget overview of projects — e.g. all of one customer — with how much of each budget is used and which are over budget. An amount budget counts the booked time's revenue and the external costs booked on the project; an hour budget the booked hours, and it is over budget too when its external costs top what the confirmed quotes sold. Basic users and up see the percentage and whether it is over; the budget itself (hours or money) only users who see it in docket; timetrackers see no budgets. Monthly budgets count the current month.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_budgets"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idNoFrom search_customers; default: all customers
include_finishedNoAlso done, canceled and archived projects (default false)
only_over_budgetNoOnly projects over budget

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / only_over_budget / description
      Previous value: -"Only projects above 100 %"New value: +"Only projects over budget"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so much of the safety profile is free. The description still adds substantive behavioral context an agent cannot get from annotations: results vary by role (basic users see percentage and over-budget flag, budget values only for users who see them in docket, timetrackers see no budgets at all), and monthly budgets are scoped to the current month. That role-varying response shape is exactly the kind of insight annotations do not carry.

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 purpose is front-loaded and the permission details carry real value, but the middle clauses are dense semicolon run-ons ('an hour budget the booked hours, and it is over budget too when its external costs top what the confirmed quotes sold') that take work to parse. It would read better as short bulleted conditions.

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

Completeness4/5

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

With no output schema, the description carries the burden of explaining results, and it does: percentage used, over-budget status, conditional budget amounts, plus monthly scoping. What is missing is result ordering and any note about volume or pagination for large project portfolios.

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 all three parameters are already documented in the schema, and the description's 'all of one customer' merely echoes the customer_id default of all customers. It does not clarify the external-cost or quote-based over-budget rule's interaction with the only_over_budget flag, so it adds little beyond the schema baseline.

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 a specific verb and resource ('Budget overview of projects') and defines what the metrics mean: amount budgets count booked revenue plus external costs, hour budgets count booked hours. It never names a sibling, so the agent must infer that this is the per-project budget view rather than financial_summary or revenue_forecast, but the scope is otherwise unambiguous.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'e.g. all of one customer' signals that this is used for customer-scoped portfolio views, and the permission notes tell the agent which roles get results. There is no explicit when-not guidance and no routing to alternatives such as search_projects or financial_summary for related questions.

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