Skip to main content
Glama

exchange_status

Retrieves KrystalineX exchange operational state, uptime, observability posture, and last incident summary to help agents assess system health.

Instructions

Get the KrystalineX exchange overall status: operational state, uptime, current observability posture, and last incident summary.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. The verb 'Get' and the field list imply a safe read-only call returning a current-state snapshot, which is useful, but nothing is said about data freshness, caching, or the limits of the response.

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?

It is one sentence with the resource and scope front-loaded, followed by a compact list of the returned fields. Nothing is repeated, and nothing is wasted.

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

Completeness3/5

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

There is no output schema, so the description must explain what comes back, and it names the four field groups but does not give formats or units (for example, is uptime a percentage or a duration?). It is enough for an agent to decide to call it, but not enough to interpret the response confidently.

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 tool takes zero parameters, so the baseline is 4. Nothing in the description misdescribes the input surface, and no parameter meaning needs to be added.

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?

The description states a specific verb and resource ('Get the KrystalineX exchange overall status') and enumerates the contents: operational state, uptime, observability posture, and last incident summary. It does not explicitly distinguish itself from the similarly named sibling system_health.

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

Usage Guidelines2/5

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

It offers no when-to-use or when-not-to-use guidance, and no alternatives are named even though system_health, metrics_alerts, and anomalies_active exist. The phrase 'overall status' hints at a summary-level call, but nothing states whether to use this before or instead of those siblings.

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