Skip to main content
Glama

AICTIONBOT™ Werkbank

Find the procurement pain points that match a situation described in the user's own words

find_painpoint
Read-onlyIdempotent

Takes a situation in the user's words, for example 'invoices arrive without a purchase order' or 'the approver left and nobody can release', and returns up to three matching pain points from the Atlas with field, title and, for the 12 open ones, a short description. Keyword match without AI over titles and descriptions; if nothing fits, call atlas_overview and pick from the map. Then read the detail with get_painpoint.

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": {
      "situation": "<situation>"
    },
    "name": "find_painpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer and of the titles searched. Default de.
situationYesThe situation in one or two sentences, in German or English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, idempotent, closed-world), and the description adds genuinely new behavior: keyword matching with no AI over titles and descriptions, a hard cap of three results, and the fact that only the 12 open pain points carry descriptions. It does not mention latency or what an empty result looks like, but the fallback instruction covers the practical consequence.

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

Conciseness5/5

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

Front-loaded with what the tool does and its return shape, then the matching mechanism, then the fallback and next step. No filler; even the specific '12 open ones' detail carries useful information about result completeness.

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 does well by naming the returned fields and the result cap. A minor gap remains around how ties or zero matches are reported, though the atlas_overview fallback mitigates this.

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; the description adds value with concrete example situations ('invoices arrive without a purchase order', 'the approver left and nobody can release') that show the expected granularity and phrasing, which the schema's 'one or two sentences' does not convey. It does not elaborate on the language enum beyond what the schema states.

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 (find/takes) and resource (pain points from the Atlas), plus result shape: 'returns up to three matching pain points ... with field, title and, for the 12 open ones, a short description.' It is clearly distinguishable from get_painpoint (detail) and atlas_overview (browse the map).

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

Usage Guidelines5/5

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

Gives explicit routing: use this when the user describes a situation in their own words; if nothing fits, call atlas_overview and pick from the map; then read the detail with get_painpoint. Both the fallback path and the follow-up step are named.

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.