Skip to main content
Glama

get_process_mining_findings

Read-only

Retrieve read-only process mining findings—automated issues like rework, extra steps, extreme durations, KPIs, plus finding definitions and AI analysis—for one or all projects.

Instructions

Process Mining findings: automated findings (promin_automated_finding: rework, extra steps, extreme durations, with impacted KPIs, table and field), finding definitions (promin_finding_def) and AI analysis results (promin_gen_ai_analysis_result), for one project or all. Read-only

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows per list (default 50)
projectNoProject sys_id, number (PRO...) or name. Omit for all projects

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the trailing 'Read-only' simply repeats that, earning no credit. The description does add useful composition detail (impacted KPIs, table and field, definitions, AI results), but says nothing about ordering, pagination across the implied multiple lists, or result size behavior beyond the limit parameter.

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 core resource is front-loaded and the parenthetical enumeration of table names is compact and informative. It is a single dense run-on sentence, which hurts scannability slightly, but no sentence is filler.

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 carries the burden of telling the agent what comes back, and it does so by naming the three finding collections and their contents. What remains unclear is whether the response is one merged list or several per-entity lists, which the 'Max rows per list' parameter only hints at.

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 both parameters (limit, project) are already fully documented with defaults and accepted identifier formats. The description's phrase 'for one project or all' duplicates the schema rather than adding format or edge-case meaning, making the baseline 3 appropriate.

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 names the resource precisely and enumerates the three entity types returned (promin_automated_finding, promin_finding_def, promin_gen_ai_analysis_result) plus the specific finding categories like rework, extra steps, extreme durations. That is well beyond a restated name. It does not, however, distinguish itself from near-siblings such as get_instance_scan_findings, so it falls 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 explicit when-to-use or when-not guidance and no routing to alternatives. The only scoping hint, 'for one project or all', merely restates the schema note 'Omit for all projects', so the agent gets no new decision criteria for choosing this tool over its siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools