Skip to main content
Glama

Daily Burndown Target

bpj_daily_burndown_target
Read-onlyIdempotent

Calculate the ideal daily burn from start-of-day backlog and compare the day’s actual completion with that pace.

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": {
      "scope": "<scope>",
      "days": "<days>",
      "done": "<done>"
    },
    "name": "bpj_daily_burndown_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
doneYes
scopeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, and non-destructive behavior, so safety is covered. The description adds that the tool computes a pace and compares actual completion, but it omits the result format, rounding behavior, and any edge-case semantics beyond the schema constraints.

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?

The description is a single front-loaded sentence with no redundant wording. Every phrase contributes to the tool's purpose.

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?

This is a simple three-parameter calculation with rich annotations, but there is no output schema. The description does not explain what the comparison returns, such as a variance, ratio, or ideal target, which is a meaningful gap for an agent interpreting the result.

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 needs to carry parameter meaning. It maps scope to start-of-day backlog and done to actual completion, but it never mentions days as remaining working days or states the division relationship, leaving one parameter's role implicit.

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 computation: calculate an ideal daily burn and compare actual completion against it. The verb and resources are clear, but it does not explicitly name the return shape or distinguish itself from any conceptually similar tool.

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?

There is no explicit when-to-use guidance, no prerequisites, and no alternatives. The agent can infer this is for burndown tracking, but the description itself gives no conditions for selecting it.

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.