Skip to main content
Glama

get_data_quality_status

Read-onlyIdempotent

Assess the operational status of crypto market data APIs. Returns health metrics, latency, completeness, and incident count for each venue and data type.

Instructions

Get the current system status for supported venue APIs and data types. Returns overall health (operational/degraded/outage), per-scope status with latency, per-data-type completeness, and active incident count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResult data object

Implementation Reference

  • src/index.ts:1927-1936 (registration)
    Registration of the 'get_data_quality_status' tool using the registerTool helper. The tool has no input parameters, uses ObjectOutputSchema as output, and calls api().dataQuality.status() to fetch system status data.
    registerTool(
      "get_data_quality_status",
      "Get the current system status for supported venue APIs and data types. Returns overall health (operational/degraded/outage), per-scope status with latency, per-data-type completeness, and active incident count.",
      {},
      ObjectOutputSchema,
      async () => {
        const data = await api().dataQuality.status();
        return formatResponse(data);
      }
    );
  • Handler function for get_data_quality_status. It calls api().dataQuality.status() and formats the response. Returns overall health (operational/degraded/outage), per-scope status with latency, per-data-type completeness, and active incident count.
    async () => {
      const data = await api().dataQuality.status();
      return formatResponse(data);
    }
  • ObjectOutputSchema used by get_data_quality_status. Defines a single 'data' field as a record of unknown values, used for tools that return a single object (current snapshots, orderbooks, data quality).
    const ObjectOutputSchema: ZodRawShape = {
      data: z.record(z.unknown()).describe("Result data object"),
    };
Behavior3/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds detail on return fields but does not disclose additional behavioral traits (e.g., caching, rate limits).

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 a single, front-loaded sentence that covers the key purpose and return fields without extraneous information. Slightly dense but efficient.

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 annotations covering safety and an output schema existing, the description adds necessary context about the return structure. The tool is well-documented given its simplicity.

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

Parameters4/5

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

The input schema has zero parameters, so the description correctly adds no parameter details. Baseline score of 4 applies per guidelines.

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 tool retrieves current system status for venue APIs and data types, listing specific return fields (overall health, per-scope status, etc.). It is distinct from sibling tools like get_data_coverage or get_data_incidents.

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 this is for a high-level status overview but does not explicitly state when to use it instead of more specific sibling tools (e.g., get_data_latency). No exclusions or alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/0xArchiveIO/0xarchive-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server