Skip to main content
Glama

AICTIONBOT™ Werkbank

Symptom navigator: nine typical procurement problems rated 1 to 5, per symptom what it costs, the first step and the matching tools, plus the matching step of the KULIC ladder

navigate_symptoms
Read-onlyIdempotent

Rate nine symptoms from 0 to 5: manual (manual work), approvals (nested approvals), visibility (no spend overview), data (wrong or duplicate data), suppliers (difficult supplier relationships), compliance (rule breaches), maverick (orders bypassing procurement), communication, breaks (system breaks). Returns per symptom, strongest first, what it typically costs, the first step for this week and the matching Workbench tools, and the matching step of the KULIC ladder with the step below and above (no prices in the answer; prices on the linked pages). has_procurement no keeps the recommendation at Signal Scan or below. Licence, or one free check every 30 days.

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": {
      "symptoms": "<symptoms>"
    },
    "name": "navigate_symptoms"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer. Default de.
symptomsYesStrength per symptom from 0 (does not apply) to 5 (fully applies).
has_procurementNoIs there a procurement department?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / symptoms / properties / approvals / description
      Added value: +"Slow approvals: 0 to 5."
    • addedInput schema / properties / symptoms / properties / breaks / description
      Added value: +"Breaks between systems: 0 to 5."
    • addedInput schema / properties / symptoms / properties / communication / description
      Added value: +"Friction between departments: 0 to 5."
    • addedInput schema / properties / symptoms / properties / compliance / description
      Added value: +"Rules not followed: 0 to 5."
    • addedInput schema / properties / symptoms / properties / data / description
      Added value: +"Poor master data: 0 to 5."
    • addedInput schema / properties / symptoms / properties / manual / description
      Added value: +"Manual work and lists: 0 to 5."
    • addedInput schema / properties / symptoms / properties / maverick / description
      Added value: +"Buying past procurement: 0 to 5."
    • addedInput schema / properties / symptoms / properties / suppliers / description
      Added value: +"Too many or the wrong suppliers: 0 to 5."
    • addedInput schema / properties / symptoms / properties / visibility / description
      Added value: +"No overview of spend and status: 0 to 5."
  2. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. Beyond that the description adds real context: results are ordered strongest symptom first, the answer contains no prices (prices live on linked pages), a licence is required with one free check every 30 days, and has_procurement=no caps the recommendation at Signal Scan or below. The only miss is that 'one free check every 30 days' is stated telegraphically and the shape of the returned report stays abstract.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening 'Rate nine symptoms from 0 to 5' is well front-loaded, but the rest is a single run-on sentence that merges the symptom list, output description, pricing note, gating rule and licensing into one block. The parenthetical glosses duplicate schema descriptions and the closing 'Licence, or one free check every 30 days.' is fragmented. Trimming the repeated symptom definitions would sharpen it considerably.

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?

With no output schema, the description carries the burden of describing returns, and it does list cost, first step, matching tools and KULIC step plus the step below and above. However it never says whether all nine symptoms must be supplied (the nested object has no required fields), and the title says 'rated 1 to 5' while the description and schema say 0 to 5, leaving a minor contradiction an agent must resolve. The licence and rate-limit note is present but too terse to act on confidently.

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 coverage is 100%, so each of the nine symptom keys and the language enum are already documented in the schema, and the description's parenthetical glosses largely restate them. It does add genuine meaning for has_procurement by explaining that 'no' clamps the recommendation to Signal Scan or below, and it explains the ordering of results. That is useful but narrow against a three-parameter tool whose schema does the heavy lifting, so baseline 3 fits.

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 states a concrete verb and resource: rate nine named procurement symptoms (manual, approvals, visibility, data, suppliers, compliance, maverick, communication, breaks) and return cost, first step, matching tools and KULIC ladder position. That is far more specific than the name alone and lets an agent recognise it as a diagnostic/assessment tool. It does not explicitly contrast itself with assessment siblings such as analyse_issues or assess_team, 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 statement of when to reach for this tool versus the many sibling analysis tools, and no prerequisites are spelled out beyond the licence note. The closest thing to guidance is 'first step for this week' and the has_procurement gating, which describe output behaviour rather than tool selection. An agent must infer the use case from the symptom list alone.

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.