Create a NiFi parameter context with named parameters, then bind it to a process group to centralize reusable configuration values.
Create a parameter context with parameters. Bind it to a group with nifi_bind_parameter_context.
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, covering the safety/idempotency profile. The description adds no behavioral context beyond that—nothing about uniqueness of names, error behavior, or side effects. With annotations carrying the disclosure burden, the description contributes essentially nothing extra.
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?
Two short, front-loaded sentences with zero filler. The core action comes first and the follow-up hint comes second.
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?
An output schema exists, so return values need not be explained, and annotations cover the mutation/safety profile. Still, for a create tool the description omits name-uniqueness constraints and failure modes, leaving the agent with only the minimal action statement plus one next-step pointer.
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?
The single top-level 'params' object parameter has no schema description (0% reported coverage). The description says only 'with parameters', which does not explain the nested name/value/sensitive/description fields or clarify the object shape. Although the nested $defs carry useful detail, the top-level parameter is left undocumented and the description does not compensate.
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?
States a specific verb+resource: creating a parameter context with parameters. It also hints at downstream use by naming nifi_bind_parameter_context, which helps separate it from read/update siblings. It is clear but does not explicitly contrast with nifi_update_parameter_context or nifi_get_parameter_context.
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?
The description implies the workflow ('Bind it to a group with nifi_bind_parameter_context'), giving a next-step cue. But it offers no guidance on when to create vs. update an existing context, prerequisites, or what happens if a context with the same name already exists.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.