Skip to main content
Glama

list_process_mining_projects

Read-only

Retrieve Process Mining projects with status, last mined date, templates, and automated-findings counts to review project activity and coverage.

Instructions

Process Mining (Process Intelligence) projects (promin_project): table, status, when last mined, templates, and how many automated findings each has. 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": "list_process_mining_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax projects (default 50)
include_templatesNoInclude template projects (default false)

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, so 'Read-only' largely restates what the agent already knows. The genuinely additive part is disclosing the shape of returned rows (status, last-mined timestamp, template flag, count of automated findings), which tells the agent this is a summary-level call, not a detail fetch. It says nothing about ordering, pagination behavior when limit is exceeded, or what an empty result means.

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?

A single dense sentence, front-loaded with the resource name and the internal promin_project key, followed by the payload contents. The nested parentheses ('Process Mining (Process Intelligence)') are slightly cluttered but each clause carries information.

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?

There is no output schema, and the description compensates well by enumerating the fields returned per project, so an agent can anticipate the response. Combined with annotations covering the safety profile, the only real gap is routing guidance relative to sibling list/get tools, which is a usage concern rather than a completeness one.

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 (limit, include_templates) carry their own defaults, so the schema carries the parameter burden. The description mentions 'templates' as a returned attribute, which loosely connects to include_templates, but adds no syntax, range, or behavioral detail beyond the schema.

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 specific resource (Process Mining / Process Intelligence projects, with the underlying promin_project identifier) and enumerates what each row reveals (table, status, last-mined time, templates, automated finding counts). It is clearly a listing tool, though it never explicitly contrasts itself with siblings such as list_projects or get_process_mining_findings.

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?

Aside from the closing 'Read-only' note, there is no guidance on when to call this versus list_projects (which sounds like a broader project listing) or get_process_mining_findings (the per-project drill-down). The agent must infer the boundary between listing projects and fetching their findings.

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