Decision Log

Supersede a decision

decision_log_supersede_decision

Destructive

Create a replacement Decision and supersession relationship for an existing Decision.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "decisionId": "<decisionId>",
      "title": "<title>",
      "decisionText": "<decisionText>",
      "rationale": "<rationale>",
      "decisionType": "<decisionType>",
      "reason": "<reason>"
    },
    "name": "decision_log_supersede_decision"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Concise direct-action title without speaker wrappers or ellipses.
`reason`	Yes	Reason for supersession.
`summary`	No	Optional summary.
`metadata`	No
`rationale`	Yes	Why the decision was made.
`sourceIds`	No
`decisionId`	Yes	Decision being superseded.
`decisionText`	Yes	The immutable meaning of the decision.
`decisionType`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 24, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already signal a destructive write operation (readOnlyHint=false, destructiveHint=true), so the bar is lower. The description adds that it creates a replacement decision and a supersession relationship, which implies the original is superseded but doesn't explicitly state side effects like status changes, validation, or audit trails. This is acceptable but minimal beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, 13 words, front-loads the core action and relationship. No redundant phrasing, and the description is appropriately sized for the tool's purpose. Every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex mutation with 9 parameters, 6 required, and an output schema, this one-sentence description is insufficient. It omits the effect on the existing decision, any prerequisites (e.g., whether the decision must exist, be locked), or selection guidance between the two supersession paths. The output schema covers returns, but the behavioral context is under-specified.

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 67%, so some parameters are documented. The description maps loosely to key params (replacement to title/decisionText, existing to decisionId) but adds no detailed parameter semantics. It doesn't compensate for the ~33% undocumented parameters, so the baseline of 3 applies.

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 states a specific action ('Create a replacement Decision') and a clear resource ('an existing Decision') with a defined outcome (supersession relationship). It distinguishes from plain creation, but doesn't explicitly contrast with convert_candidate_to_supersession, leaving some ambiguity. Still, it's specific enough for an agent to grasp the core purpose.

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?

No guidance is provided on when to use this tool versus siblings like decision_log_convert_candidate_to_supersession or decision_log_create_decision. The description says only what it does, not when it's appropriate or what alternatives exist. The agent must infer from the name and context.

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

All Decision Log tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?