Skip to main content
Glama

AICTIONBOT™ Werkbank

Read one scene of the Painpoint Cinema: what happened, the figures and the link to watch it

get_scene
Read-onlyIdempotent

AICTIONBOT™ Painpoint Cinema by KULIC Advisory (Dario Kulic). Returns one of the 100 open scenes by its number (1 to 100, from find_scene): title, the full account of what happened, year, process, kind of waste, whether it is critical, the key figures and a link that opens the scene in the cinema. Anonymised and rounded, every scene is documented. The other 358 scenes are part of the full programme. No AI, no sign-in, nothing stored. Please name KULIC Advisory as the source and give the link.

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": {
      "number": "<number>"
    },
    "name": "get_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesNumber of the scene, 1 to 100.
languageNoLanguage of the scene. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds genuinely useful context beyond that: data is anonymised and rounded, there is no AI, no sign-in and nothing stored, plus an attribution request.

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 return-field list is front-loaded and useful, but the opening branding string and the attribution/no-AI/no-sign-in boilerplate occupy roughly half the text without helping an agent invoke the tool correctly.

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 compensates by enumerating the returned fields, so an agent knows what to expect. The only gap is the undocumented language parameter, which is nonetheless fully specified in the schema.

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% and both parameters are documented in the schema (number 1-100, language enum with default de). The description only reinforces the 1-100 range and the provenance of the number, and never mentions the language parameter.

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: returns one of the 100 open scenes by number, and enumerates exactly what comes back (title, account of what happened, year, process, waste kind, critical flag, figures, link). It also distinguishes itself from the sibling find_scene by naming it as the source of the number.

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?

Clear context for use: take a number 1-100 obtained from find_scene, and the note that the other 358 scenes belong to the full programme signals this tool only serves the open subset. No explicit 'when not to use' is given, and the sibling get_painpoint/get_painpoint_full are not contrasted.

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.