Recent verification changelog (cancelflow).
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": "cancelflow_changes"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full burden and does not meet it. It does not say whether the tool is read-only, how far back 'recent' reaches, how many entries are returned, or what fields an entry contains.
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?
It is a single short phrase with no padding, which is good, but it is under-specified rather than concise. 'Verification changelog' is unexplained jargon that adds ambiguity instead of information.
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?
With no annotations, no output schema, and no parameters, the description is the only source of behavioral information, and it says almost nothing about return shape, recency window, or ordering. An agent cannot confidently predict what calling this tool produces.
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 tool takes zero parameters, so there is nothing for the description to clarify beyond the schema, and the baseline for a parameterless tool is a 4. The description does not misrepresent the absence of inputs.
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 identifies the resource as a 'recent verification changelog' scoped to cancelflow, which hints at returning recent changes. However, it omits a verb, does not say what is being changed (facts? rules? data?), and never distinguishes it from siblings like cancelflow_get_fact or cancelflow_list_facts, so the agent must infer the purpose.
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?
There is no when-to-use guidance and no mention of the sibling tools cancelflow_get_fact or cancelflow_list_facts as alternatives. The word 'Recent' is the only implicit usage cue, leaving the agent to guess whether this is a sync/diff feed or a browse endpoint.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.