Forwardsmith buyer desk (read-only)

Add up published starting prices

estimate_engagement

Read-onlyIdempotent

Adds up the published starting prices for a chosen path of one to three steps (mapping, sprint, fde). Returns the lines, the sum as a lower bound in EUR excl. VAT, what is not included and what is not published. No discounts, no new prices, not a quote.

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": {
      "path": "<path>"
    },
    "name": "estimate_engagement"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No		en
`path`	Yes

Output Schema

Name	Required	Description	Default
`vat`	Yes
`lines`	Yes
`notes`	Yes
`source`	Yes
`currency`	Yes
`stop_rule`	Yes
`price_type`	Yes
`not_included`	Yes
`not_published`	Yes
`sum_of_starting_prices`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely useful behavior: the result is itemized lines plus a sum, the sum is a lower bound in EUR excluding VAT, and it enumerates what is excluded and unpublished. That 'lower bound / not a quote' caveat is exactly the kind of context an agent needs before relaying a number to a user, though nothing is said about precision, currency conversion, or latency.

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 sentences, front-loaded with the action, with no filler or restatement of the title beyond the necessary scope. The telegraphic ending ('what is not included and what is not published') is slightly compressed but still parses correctly.

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 an output schema present, the description need not enumerate return fields, yet it still characterizes the result shape and its lower-bound caveat, which is valuable. The only real gap is the undocumented `lang` parameter for a low-complexity, two-parameter, single-object tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 carry the parameter meaning, and it does for the required `path`: one to three steps drawn from mapping, sprint, and fde, which matches the enum, minItems/maxItems, and uniqueness constraints. The `lang` parameter (en/nl, default en) is never mentioned, leaving one of two parameters undocumented in both schema and description.

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 opens with a specific verb and resource: it 'adds up the published starting prices' for 'a chosen path of one to three steps (mapping, sprint, fde)', and the closing negations ('No discounts, no new prices, not a quote') pin down its scope precisely. It does not name or distinguish itself from a sibling such as get_offers, so an agent must infer the boundary between estimating a bundle and retrieving an offer.

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: an agent can infer it is used to price a 1-3 step combination, and the exclusions ('no discounts... not a quote') exclude some interpretations. There is no explicit when-to-use, when-not-to-use, or named alternative for the case where a real quote or discount-adjusted price is needed.

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

All Forwardsmith buyer desk (read-only) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?