Meta Council

Dismiss ticket integration effect

dismiss_ticket_integration_effect

Idempotent

Settle one uncertain effect as owner-dismissed: you accept that its outcome stays unknown. Requires confirm true; makes no provider request and records one immutable settlement. A dismissed create can allow a later new create, so a duplicate remote item is the owner’s risk. Never retries or replays the effect. Refused until the deploy-owned settlement activation (graph v3). An effect left cancelled with attempt_count 1 cannot be dismissed. If an outcome is unconfirmed, read list_ticket_integration_effects_v2 before another action. Requires integrations:write and tickets:write.

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": {
      "provider": "<provider>",
      "effect_id": "<effect_id>",
      "confirm": "<confirm>"
    },
    "name": "dismiss_ticket_integration_effect"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	Yes
`provider`	Yes
`effect_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, it discloses that no provider request is made, one immutable settlement is recorded, retries/replays never happen, and there is a duplicate-remote-item risk owned by the user. It also states required permissions (integrations:write and tickets:write) and the activation dependency, which annotations do not cover.

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?

The description is front-loaded with the core action and then adds preconditions, risks, and permissions. It is information-dense and nearly every sentence contributes, though a few clauses could be tightened.

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

Completeness5/5

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

For a complex mutation with no output schema, the description covers purpose, side effects, idempotency behavior, authorization requirements, preconditions, and the relevant read-before-action tool. Parameter details are largely constrained by the schema, so the description is complete enough to invoke safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains only confirm (must be true) and vaguely refers to 'one uncertain effect'; it does not explain the provider enum values or the UUID format/semantics of effect_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first clause gives a specific verb and resource: 'Settle one uncertain effect as owner-dismissed.' It also distinguishes the operation from siblings by stating it makes no provider request, unlike confirm/reconcile/retry tools, and it names the related read tool list_ticket_integration_effects_v2.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit preconditions and exclusions: confirm must be true, the tool is refused until the settlement activation, and an effect left cancelled with attempt_count 1 cannot be dismissed. It also tells the agent to read list_ticket_integration_effects_v2 when an outcome is unconfirmed before taking another action.

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

All Meta Council 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?