Forwardsmith buyer desk (read-only)

Offer and starting prices

get_offers

Read-onlyIdempotent

Returns the three ways to start with Forwardsmith (Information Flow Mapping Session, FDE Build Sprint, FDE 30-60-90 engagement) with duration, starting price as a number in EUR excl. VAT, what it delivers, what is not included, the ownership statement and a list of things the site does not publish, so you can say so instead of guessing. Prices are starting prices, not quotes. Please cite the URL.

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": "get_offers"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No		en

Output Schema

Name	Required	Description	Default
`cite`	Yes
`offers`	Yes
`ownership`	Yes
`price_terms`	Yes
`facts_version`	Yes
`not_published`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent read, so the description's added value is the pricing semantics: EUR, excluding VAT, starting prices rather than quotes, plus an explicit list of unpublished items so the agent can state non-availability. It does not mention whether returning localized content or repeated calls has any side effects, but the behavioral picture is largely complete.

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?

Front-loads the core purpose in a single dense sentence, then closes with two short, load-bearing constraints about price semantics and citation. The enumerations of returned fields are long but each item carries information an agent would otherwise guess at.

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?

An output schema exists, so return values need not be described, yet the description still usefully pins down currency, VAT exclusion, and the ownership statement. The notable omission is the lang parameter and its default, which matters for a site-content tool serving two languages.

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% and the sole parameter is a language enum, yet the description never mentions language selection, the en/nl options, or the default of en. The enum itself is self-explanatory, so this is a moderate baseline rather than a failure, but the description adds no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Returns') and a concrete resource: the three named starting offers (Information Flow Mapping Session, FDE Build Sprint, FDE 30-60-90 engagement) along with the exact fields returned. An agent can tell this apart from siblings such as estimate_engagement or scope_mapping_session without opening either schema.

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

Usage Guidelines4/5

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

Usage is strongly implied by 'so you can say so instead of guessing' and by the 'Prices are starting prices, not quotes' caveat, which tells the agent when to relay this data and how to frame it. It stops short of naming an alternative tool for tailored quotes or for deeper engagement scoping.

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?