AICTIONBOT™ Werkbank

Turn one sentence into a scope of work for a request for quotes (AICTIONBOT™ scope writer)

write_scope_of_work

Read-only

Needs the user's AICTIONBOT™ Werkbank licence; each call uses one AI analysis from the licence quota. Turns a short description of what a business wants to buy into a structured scope of work for a tender or request for quotes: subject, work packages with deliverables, exclusions, supplier requirements, service levels, volume assumptions, questions to bidders, award criteria with weights and points to clarify internally. Placeholders where facts are missing; nothing is invented.

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": {
      "request": "<request>"
    },
    "name": "write_scope_of_work"
  }
}

Input Schema

Name	Required	Description
`details`	No	Optional additional facts: places, quantities, dates, budget, special requirements.
`request`	Yes	What is to be bought, in one or two sentences, e.g. 'Office cleaning for 2 sites in Cologne, 5 days a week, from January'.
`language`	No	Language of the answer: de, en, fr, es, pt or zh. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds real behaviour beyond the annotations: an AICTIONBOT™ Werkbank licence is required, each call burns one AI analysis from the quota (consistent with idempotentHint=false), and missing facts appear as placeholders rather than being invented. That last point is a meaningful quality guarantee an agent cannot infer from the schema.

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 licence/quota constraint before the purpose, which is the right order for a metered tool. The long middle sentence is dense but each listed element corresponds to actual output content; little 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?

With no output schema, the description carries the burden of describing the return value and does so by enumerating the scope sections produced, plus the placeholder policy. Only the response format and approximate size remain unspecified.

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 100%, so the schema already documents request, details and the language enum with the German default. The description only restates that the input is a short description of what is to be bought, adding no format, length or quality guidance 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 transformation: a short purchase description becomes a structured scope of work for a tender/RFQ. The enumerated output components (subject, work packages, exclusions, supplier requirements, SLAs, award criteria) make it unmistakable against siblings like write_meeting_minutes or compare_offers.

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?

Implies the use case (tendering/RFQ preparation) and states a licence prerequisite, but never says when to prefer this over alternatives or what input is too thin to qualify. No explicit exclusions or routing guidance.

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

All AICTIONBOT™ Werkbank 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?