Skip to main content
Glama
Sign In
x5-mcp

x5-mcp

by DashinIN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

x5_get_categories

Read-onlyIdempotent

Retrieve category codes and item counts for purchases within a specified date range, with optional grouping by day, week, or month and network filter.

Instructions

Исходные коды категорий и число позиций. Названия категорий не выдумываются.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "x5_get_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
groupByNomonth
networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful output context: it returns source category codes and counts, and warns against inventing category names. However, it does not explain grouping behavior, date-range semantics, or response format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very brief, but brevity here crosses into under-specification. It is a fragment plus a warning, with no structured explanation of the operation, parameters, or output. It is not appropriately concise; it is simply incomplete.

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

Completeness2/5

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

With no output schema, the description needed to describe return values and parameter meaning, but it only gives a minimal hint about category codes and counts. The date range, grouping options, network selection, and relationship to similar category tools are left unexplained, making this inadequate for reliable invocation.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must explain the parameters, but it does not mention from, to, groupBy, or network at all. The only meaningful content is about categories and counts, which does not clarify how to set any of the four parameters correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as categories and hints at the output (source codes and item counts), but it is a noun phrase with no explicit verb like 'returns' or 'gets'. It also does not distinguish this tool from siblings such as x5_get_category_spending, so the purpose remains somewhat vague.

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?

There is no guidance about when to use this tool versus alternatives, no exclusions, and no context about date ranges or network filters. The sentence 'Названия категорий не выдумываются' is an instruction about output handling, not usage guidance.

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