Skip to main content
Glama
Sign In
0xarchive-mcp

0xarchive-mcp

by 0xArchiveIO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_data_incidents

Read-onlyIdempotent

List data quality incidents with filters for status, exchange, or time. Get severity, duration, root cause, and resolution details.

Instructions

List data quality incidents (outages, gaps, degradations). Filter by status, exchange, or time. Returns incident details including severity, affected data types, duration, root cause, and resolution.

Tool call template

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": "get_data_incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter incidents by status
exchangeNoVenue scope
sinceNoOnly incidents after this time (Unix ms or ISO)
limitNoMax results (default 20, max 100)
offsetNoPagination offset

Output Schema

NameRequiredDescriptionDefault
dataYesResult data object

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.9.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds that results include severity, duration, etc., but does not disclose additional behavioral traits like rate limits or auth requirements. No contradiction with 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?

Two concise sentences with front-loaded purpose, filtering options, and return details. Every sentence adds value without redundancy.

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 a complete output schema and 5 optional parameters (2 with enums), the description sufficiently covers the tool's functionality. No critical gaps remain for a list endpoint.

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 100% with all 5 parameters described. The description reinforces filtering by status, exchange, and time but does not add new semantic meaning beyond what the schema provides. Pagination parameters (limit, offset) are omitted from the description.

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 clearly states the verb 'List' and the resource 'data quality incidents', providing concrete examples (outages, gaps, degradations) and mentioning return fields. It distinguishes from siblings like get_data_coverage by focusing on incidents specifically.

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?

The description implies filtering capabilities but does not explicitly state when to use this tool vs alternatives like get_incident (singular). No 'when not to use' or comparative guidance is provided.

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

Deploy Server

Other Tools