Forwardsmith buyer desk (read-only)

FDE Readiness Scan

run_readiness_scan

Read-onlyIdempotent

Runs the same six-question FDE Readiness Scan as the page on forwardsmith.com, with the same scoring. Returns the score, the recommended starting point with its starting price, what is already in place and what to prepare. Indicative self-assessment, 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": {
      "answers": "<answers>"
    },
    "name": "run_readiness_scan"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`why`	Yes
`offer`	Yes
`answers`	Yes
`same_as`	Yes
`disclaimer`	Yes
`to_prepare`	Yes
`score_percent`	Yes
`already_in_place`	Yes
`recommended_start`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. Beyond that, the description adds real context: scoring mirrors the public website page and the result is indicative rather than a binding quote, which tells the agent how to frame the output to a user.

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?

Three tight sentences, front-loaded with the core action and ending with the key caveat. Minor redundancy in 'the same ... with the same scoring', but nothing is wasted.

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?

For a nested-schema tool with an output schema present, the description covers purpose, return content and the non-binding nature of the result adequately. The main omission is any treatment of the 'lang' option and the answer semantics, which the schema alone leaves thin.

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 at 0%, so the description must carry weight; 'six-question' does signal that the six required nested answers map one-to-one to the scan questions. However, it never mentions the 'lang' parameter, nor any meaning of the enum values or how the answers affect scoring.

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?

The description gives a specific verb and resource ('Runs the ... FDE Readiness Scan') and pins down scope ('six-question', 'same scoring' as the public page). It also states what comes back (score, recommended starting point with starting price, what's in place, what to prepare), which separates it from siblings like estimate_engagement or check_fit.

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?

The closing line 'Indicative self-assessment, not a quote' implies this is the low-commitment alternative to a quoting/engagement tool, but no sibling is named and no explicit when-to-use or prerequisite condition is given. Guidance is inferable rather than stated.

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?