Skip to main content
Glama

Sends to integrations that failed

dosai_list_integration_failures
Read-onlyIdempotent

Data the project tried to pass to a connected service (Google Sheets, CRM, email, webhook) and could not (the latest 30): the kind, what it was about, the error, how many retries were made and when the next one is (next_retry_at null = retries are over, the data did NOT arrive). error_code names a known cause (wrong key, no access). Fix the cause (dosai_connect_crm, dosai_check_google_access, dosai_save_webhook_integration); waiting retries then go through by themselves.

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>"
    },
    "name": "dosai_list_integration_failures"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field changed
    • 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/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds substantial context on top: the 30-record cap, the fields returned, the meaning of next_retry_at null ('retries are over, the data did NOT arrive'), the interpretation of error_code, and the fact that retries may succeed on their own after a fix. That is exactly the behavior an agent needs and cannot get from structured fields.

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?

One front-loaded sentence that names the resource, the cap and the field list before moving to remediation. It is dense with parenthetical enumerations, but no clause is filler; slightly tighter punctuation would make it easier to scan.

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?

With no output schema, the description must explain the return shape, and it does: the field set, the 30-item limit, and the semantics of the two ambiguous fields (next_retry_at, error_code). Combined with one fully documented parameter and clear annotations, nothing needed to call this correctly is missing.

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?

There is a single required parameter with 100% schema description coverage, including its provenance ('From dosai_list_projects'), so the schema carries the burden. The description adds nothing about project_id or its UUID format. Baseline 3 is appropriate.

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?

States a specific resource (data the project tried to pass to a connected service that failed) plus the scope cap (the latest 30) and enumerates the returned fields. An agent can tell this is the failure log, not the integrations list. It never uses an explicit verb like 'list', which keeps it just short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the remediation sentence, which names dosai_connect_crm, dosai_check_google_access and dosai_save_webhook_integration as the fix paths. There is no explicit 'use this when' or a stated exclusion such as 'to see healthy integrations, use dosai_list_integrations', so the agent must infer the boundary.

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