Skip to main content
Glama

Proportional Budget Allocation

bpj_proportional_budget
Read-onlyIdempotent

Allocate a budget by weights, rounding with largest remainders so the shares sum to the total cents.

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": {
      "total": "<total>",
      "weights": "<weights>"
    },
    "name": "bpj_proportional_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
totalYes
weightsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuine behavioral context beyond that: it discloses the rounding algorithm (largest remainders) and the guarantee that shares sum to the total cents, which is exactly what an agent needs to predict output values.

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?

One sentence, front-loaded with the verb and resource, with the rounding guarantee appended as the key qualifier. No filler or redundant restatement of the title.

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?

With no output schema, the description should say what comes back — presumably a per-name allocation list — and it does not. Combined with the unexplained weight-line format, an agent can understand the intent but lacks the details to construct inputs and interpret results confidently.

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 0%, so the description must compensate. It does clarify that 'total' is expressed in cents and that 'weights' drive proportional shares, but it never explains the 'Name|weight' one-per-line string format or the 50-entry limit that an agent must satisfy to build a valid call. Partial compensation for a real gap.

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 ('Allocate') and resource ('a budget by weights') plus the rounding strategy, which clearly separates it from sibling budget tools like bpj_page_meta_budget or bpj_page_transfer_budget. It does not explicitly name which sibling to use instead, but the purpose itself 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 Guidelines3/5

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

Usage is only implied: the mention of largest-remainder rounding signals that this tool is for cases where shares must sum exactly to the total cents. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the selection criteria from the algorithm description.

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.