Skip to main content
Glama

AICTIONBOT™ Werkbank

Portfolio traffic light: progress against time and budget per project, overdue, over budget, no owner, reported green but calculating red, forecast at completion

check_portfolio
Read-onlyIdempotent

AICTIONBOT™ portfolio check by KULIC Advisory, built on the Execution Toolkit template T15 (transformation portfolio summary). Takes the project register (project, owner, progress in percent, start and target date, budget and spent where available, reported status, decision required, top risk) and returns per project the share of time elapsed, budget burn, schedule and cost index, a calculated traffic light with the reason (past the target date, over budget, budget burning faster than progress, progress behind time, blocked, no owner or several owners) and the projects reported green that calculate red. For the portfolio: counts per colour, average progress, budget, spent and forecast at completion, and the decisions needed. Deterministic, no AI, nothing stored. Needs sign-in: runs with an AICTIONBOT™ Werkbank licence; without a licence one check per connection every 30 days is free (sign in with “Connect without a licence”).

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": {
      "projects": "<projects>"
    },
    "name": "check_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoReference date, YYYY-MM-DD. Default today.
languageNoLanguage of the answer. Default de.
projectsYesRows: project, owner, progress (percent), start, target (end date), budget, spent, rag (reported status), status, decision_required, top_risk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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/non-destructive/closed-world, and the description still adds real behavior: deterministic with no AI, nothing stored, an authentication requirement and a quantified quota (one check per connection every 30 days without a licence). It does not cover failure behavior or how incomplete budget/spent values are handled, which keeps it below a 5.

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 core content is dense and useful, but it opens with branding and a template identifier ('AICTIONBOT™ by KULIC Advisory, built on the Execution Toolkit template T15') that does not help an agent decide or invoke. The remainder is a single sprawling sentence rather than being broken into what-it-takes / what-it-returns structure.

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?

There is no output schema, so the description must carry the return contract, and it does: per-project time share, budget burn, schedule and cost index, traffic light with named reasons, green-reported-but-red list, plus portfolio counts per colour, averages, forecast at completion and decisions needed. Nothing an agent needs to call or interpret this tool is missing.

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 as_of, language and the projects array with its row fields. The description restates the row semantics (progress in percent, budget and spent where available, reported status) but adds nothing about as_of or language, so it earns only the baseline.

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 and resource — takes a project register and returns per-project schedule/cost indices plus a calculated traffic light, and portfolio-level aggregates. The concrete field list (progress, budget, spent, rag, decision_required, top_risk) and the explicit outputs make it unmistakably different from generic check_* siblings.

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?

Usage is implied by the input contract: it is a portfolio-level roll-up over a register rather than a single-item check, and the description names prerequisites (sign-in, licence, one free check per 30 days per connection). However, it never states when to prefer this over siblings such as check_kpis or check_actions, nor any when-not-to-use condition.

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.