Skip to main content
Glama
Sign In
x5-mcp

x5-mcp

by DashinIN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

x5_get_sync_status

Read-onlyIdempotent

Assess data readiness before analysis by checking sync coverage, freshness, network status, and last synchronization results.

Instructions

Покрытие истории, сети, свежесть и результаты последних синхронизаций. Проверять перед аналитикой.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

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, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about which aspects the tool reports (network, freshness, last sync results) but does not disclose output format or additional behaviors. 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 short, efficient sentences with no filler. The first sentence enumerates the status dimensions, the second gives the usage directive. Every word contributes value.

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 parameterless, read-only status tool, the description gives the essential content (what the status spans) and when to use it. There is no output schema, so a bit more detail on return shape could help, but the description provides enough for an agent to invoke and interpret the result.

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?

This tool has zero parameters and 100% schema description coverage with an empty schema. Baseline 4 applies for no-parameter tools; there are no parameter semantics to explain and the description does not mislead.

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 clearly identifies the resource (sync status) and enumerates what it covers: history coverage, network, freshness, and results of last synchronizations. It is distinguishable from sibling x5_sync_history, though it does not explicitly name the alternative. A specific verb is absent but supplied by the tool name 'get'.

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

Usage Guidelines4/5

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

The description explicitly instructs to check before analytics ('Проверять перед аналитикой'), giving clear when-to-use context. It does not mention when-not-to-use or point to alternatives like x5_sync_history, so it stops short of a 5.

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