Skip to main content
Glama

Fixed Fee Project Quote

bpj_fixed_fee_project_quote
Read-onlyIdempotent

Add contingency to estimated labor and materials, then gross up the cost base for a target margin on quoted revenue.

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": {
      "labor": "<labor>",
      "materials": "<materials>",
      "contingency": "<contingency>",
      "margin": "<margin>"
    },
    "name": "bpj_fixed_fee_project_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
laborYes
marginYes
materialsYes
contingencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine behavioral content by disclosing the order of operations (contingency first, then margin gross-up on revenue rather than on cost). It does not say whether contingency applies to materials as well as labor, nor what the returned value is.

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?

A single sentence with the computation sequence front-loaded and no filler. It is slightly over-compressed, since 'Add contingency to estimated labor and materials' reads ambiguously about scope, but nothing is wasted.

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?

For a four-parameter pure calculator with no output schema, the description should state what is produced (a quoted price/revenue figure) and the treatment of edge cases such as margin near the 99.99 maximum. It conveys the calculation model but leaves the result shape and the precise gross-up formula unstated, which is a real gap when no output schema exists to compensate.

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 reported as 0%, so the description must carry the parameter meaning, and it partly does: contingency is a cost percentage added to labor and materials, and margin is a percentage applied to quoted revenue. However, the exact formula (cost / (1 - margin) vs cost * (1 + margin)) and whether contingency is applied to materials are left ambiguous, and the schema titles are the only source for units on the other fields.

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 names a specific computation: contingency is added to labor and materials, then the cost base is grossed up for a target margin on quoted revenue. That is far more than a restatement of the name 'Fixed Fee Project Quote'. It lacks any differentiation from the many sibling calculators (cost_plus_capped_fee, supplier_delivered_quote_comparison), so it stops short of a 5.

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 when-to-use statement, no prerequisites, and no pointer to an alternative such as bpj_cost_plus_capped_fee. The formula implicitly tells the agent what inputs are expected, but nothing indicates in which pricing situations this tool is the correct choice over a sibling.

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.