Skip to main content
Glama

AICTIONBOT™ Werkbank

Service catalogue for a procurement team: what it does for whom, from which value and how fast, in three levels

build_service_catalogue
Read-onlyIdempotent

Without a list it writes a catalogue of 15 services in three levels (1 basics below the threshold, 2 quotes, negotiation and contracts for any value, 3 strategic from the threshold; default threshold 25,000 euros) with requester, response time, cycle time in working days, what the department must provide and the matching Workbench tool. With a list of the team's own services (service, level, for, from value, response time, cycle time) it checks gaps, duplicates and unrealistic times and names common services that are missing. Adds ground rules and a capacity note from the team size. Licence, or one free check every 30 days.

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

Input Schema

NameRequiredDescriptionDefault
fteNoPeople in the team (full-time equivalents).
teamNoName of the team, e.g. Procurement.
languageNoLanguage of the answer. Default de.
servicesNoOptional own services: service, level (1 to 3), for, from_value, response (days), cycle (days).
thresholdNoValue in euros from which level 3 applies. Default 25000.
response_daysNoOptional response time in working days for all services of the standard catalogue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, so the description is free to add the parts annotations cannot: the licence requirement and the one-free-check-per-30-days limit, plus what the generated catalogue will contain. The verb 'writes' is mildly ambiguous against readOnlyHint=true, but the deliverable is clearly a response document rather than a persisted record, so it is not a true contradiction.

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?

The draft-then-audit structure is front-loaded and every clause carries information, but the first sentence is a long run-on with nested parentheticals that slows parsing. Slight restructuring into two crisp sentences would earn a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 it does so concretely: requester, response time, cycle time in working days, what the department must supply, and the matching Workbench tool, plus ground rules and a capacity note. Licensing and rate constraints are also disclosed, leaving nothing an agent needs before calling it.

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 coverage is 100%, so the baseline is 3, and the description goes beyond it by explaining what the parameters do in combination: the threshold gates level 3, response_days applies uniformly across the standard catalogue, and the services array is what switches the tool into audit mode. Only the language parameter is left unmentioned.

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 names a specific artifact (a 15-service catalogue in three levels) and precisely defines what each level covers, including the threshold that separates level 2 from level 3. It also states the two distinct operating modes, so an agent knows exactly what it will get before opening the 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?

The two branches are stated explicitly: with no list the tool drafts a standard catalogue, with the team's own list it audits gaps, duplicates and unrealistic times. That is clear mode-selection guidance. It stops short of naming any sibling tool as an alternative or stating when not to use this one, so no exclusions are offered.

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.