Skip to main content
Glama

Remove a failed send from the list

dosai_dismiss_integration_failure
Destructive

Remove one entry from dosai_list_integration_failures whose retries are over, after the owner dealt with it by hand. The data of that send is NOT delivered by this, it is only taken off the list; an entry that is still being retried cannot be removed. Requires editor role.

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": {
      "project_id": "<project_id>",
      "failure_id": "<failure_id>"
    },
    "name": "dosai_dismiss_integration_failure"
  }
}

Input Schema

NameRequiredDescriptionDefault
failure_idYes
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed2 schema fields changed
    • removedInput schema / properties / failure_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-read-only mutation, and the description adds real context beyond them: the underlying send data is NOT delivered, only the list entry is removed, plus the editor-role requirement and the retry precondition. It does not address reversibility or what error surfaces if the precondition fails, so it is not fully exhaustive.

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?

Two sentences, front-loaded with the action and scope, with the retry constraint and role requirement following. The side-effect clarification ('The data of that send is NOT delivered by this') is awkwardly phrased but earns its place by preventing a destructive misunderstanding.

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

Completeness4/5

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

For a two-parameter mutation with annotation coverage and no output schema, the description covers the important pieces: what is and isn't destroyed, the retry precondition, and the required role. Only minor gaps remain (reversibility, post-failure behavior).

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 coverage is 50% — project_id is self-documented, failure_id only gets a uuid format. The description implies failure_id refers to an entry from dosai_list_integration_failures, which is a useful pointer to where the ID comes from, but it adds no format or selection detail beyond that.

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 description uses a specific verb ('Remove one entry') against a named resource ('dosai_list_integration_failures'), and even clarifies the scope (one entry whose retries are over). An agent can tell this is a dismissal/removal operation on the failure list, not a general delete of the underlying send, without opening the schema.

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

Usage Guidelines4/5

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

It states the precondition for use ('after the owner dealt with it by hand') and an explicit when-not ('an entry that is still being retried cannot be removed'), which is strong selection guidance. It falls short of 5 only because it does not name another tool as the alternative for the retry-in-progress case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources