Skip to main content
Glama
akshayadeodiaspark

luxare-retail-mcp

sales_history_report

Run a sales receipt and item sales history report by specifying a date range, company, and user. Supports advanced filter overrides for custom criteria.

Instructions

Run the Diaspark sales receipt / item sales history report (pos/point_of_sale_report/sales_receipt_with_item_report). Dates use YYYY/MM/DD format. Use raw_overrides for any of the report's other criteria fields (str1-str60, all1-all30, multiselect1-30, dec1-10, list1-10, etc).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idNoDefaults to 1
end_dateNoTransaction date range end (dt2), format YYYY/MM/DD
company_idNoDefaults to 7
start_dateNoTransaction date range start (dt1), format YYYY/MM/DD
document_idNoReport definition id, defaults to 2679
raw_overridesNoAdvanced: map of any other <tag> names in the criteria XML to raw values
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It mentions date format and raw_overrides but does not state if the tool is read-only, what happens with defaults, or any side effects.

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 sentences, front-loaded with the tool's purpose, no unnecessary words. Each sentence earns its place.

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?

No output schema, 6 parameters with nested raw_overrides. The description covers date format and raw_overrides but lacks guidance on usage context or expected output, making it minimally viable.

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?

Schema coverage is 100%, but the description adds value by emphasizing the date format and explaining raw_overrides with examples (str1-str60, etc.), which helps the agent understand dynamic usage.

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

Purpose5/5

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

The description clearly states it runs the Diaspark sales receipt/item sales history report, specifying the report path. It distinguishes from sibling tools (inventory_search, list_customers) which are unrelated.

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?

No guidance on when to use this tool versus alternatives. No prerequisites or when-not-to-use instructions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/akshayadeodiaspark/luxare-retail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server