Approve or reject business process notifications in Oracle HCM, providing comments and action payloads to complete workflow tasks.
Perform BP action via businessProcessNotifications/action/performAction.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | ||
| action | Yes | e.g. APPROVE, REJECT | |
| comment | No | ||
| notificationId | Yes |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only state readOnlyHint=false, which implies mutation but nothing about side effects, permissions, or reversibility. The description adds no behavioral context; an agent cannot infer that performing an action likely changes the notification's state or triggers downstream workflow effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single vague sentence. While short, it is under-specified rather than correctly concise; essential qualifications are missing, and there is no front-loaded information about purpose or key differentiators.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (4 parameters, nested body, no output schema) and lack of sibling differentiation, this description is far too sparse for correct invocation. The absence of valid action values, body format, or return behavior makes it incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 25% (only 'action' has a description), and the tool description does not compensate. It leaves notificationId, comment, and body (a free-form nested object) entirely unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is a near-verbatim restatement of the tool name ('Perform BP action') plus a technical endpoint reference. It does not define what a BP action is or what effect it has, nor does it distinguish from sibling tools such as hcm_approve_write or hcm_bulk_approve_notifications.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. It gives no context for selecting it over the many sibling notification/approval tools)Skip_tools and fails to mention that the 'action' parameter expects values like APPROVE or REJECT.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.