Skip to main content
Glama
Sign In
billz_mcp

billz_mcp

by asadbekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

billz_report_customers_table

Retrieve a customer statistics report table with customizable filters by date, currency, and shop IDs to analyze customer data.

Instructions

Customer statistics report table

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": {
      "start_date": "<start_date>"
    },
    "name": "billz_report_customers_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
currencyNo
end_dateNo
shop_idsNo
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as that the tool retrieves data, requires a date range, or supports pagination. The agent learns nothing about side effects or constraints.

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?

At only 4 words, the description is too short to convey necessary information. This is under-specification, not conciseness; it fails to earn its space.

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

Completeness1/5

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

Given 6 parameters, no output schema, and several sibling tools, the description is completely inadequate. It omits essential context for correct invocation, such as the report's content, filtering options, and how results are structured.

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?

With 0% schema description coverage and no parameter explanations in the description, the agent receives no help understanding the meaning of parameters like 'shop_ids', 'currency', or 'limit'. The description adds no semantic value.

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 'Customer statistics report table' indicates a report on customer statistics but lacks a verb and specific details. It vaguely suggests the tool produces a table of customer data, but does not clearly state what statistics are included, making it somewhat ambiguous.

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?

The description provides no guidance on when to use this tool compared to sibling report tools like billz_report_general_totals or billz_report_profit_loss. An agent has no context to decide between them.

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