ChartQuery MCP Server

Stats

stats

Read-only

Check infrastructure health for a specified API engine or endpoint over the last hour.

Instructions

Stats. Infrastructure health for an engine or endpoint over the last hour. Not scoped to your account or tenant. Enabled per account: HTTP 403 means contact support to activate it.

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

Input Schema

Name	Required	Description	Default
`path`	No	Specific endpoint to check, for example /v1/chart. If you also pass engine, use an endpoint from that API.
`engine`	No	API family to check, for example chart. Provide at least engine or path.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real context the schema does not: a one-hour lookback window, cross-tenant data scope, and that an HTTP 403 means the feature is not enabled and requires support contact. That 403/activation note is exactly the kind of failure-mode disclosure an agent needs before calling.

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?

Three short sentences, front-loaded with the resource and time window, then scope, then the activation caveat. The only waste is the redundant 'Stats.' opener, which duplicates the tool name.

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-optional-parameter read tool with full schema coverage and no output schema, the description covers what the tool returns conceptually (infrastructure health), its temporal scope, its tenancy scope, and its activation failure mode. Only the shape of the returned metrics is left unspecified, which is acceptable here.

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 description coverage is 100%, so both parameters are already documented including the 'at least engine or path' constraint and the engine/path consistency rule. The description's 'for an engine or endpoint' merely restates the schema, adding no new syntax or format detail.

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 gives a specific resource and scope: 'Infrastructure health for an engine or endpoint over the last hour.' That distinguishes it from account-scoped siblings such as usage, though the bare lead word 'Stats' adds nothing beyond the name.

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?

It clarifies data scope ('Not scoped to your account or tenant'), which implies this is the tool for platform-level health rather than account metrics, but it never names an alternative sibling or states when-not to use this tool. Usage is inferable rather than explicit.

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

Deploy Server