get_hsn_summaryPer-HSN-code tax rollup (taxable value, CGST/SGST/IGST/cess, invoice count) for a period.
| Name | Required | Description | Default |
|---|---|---|---|
| period | No | Reporting period: mtd (default), last-month, qtd, or ytd. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {},
+ "type": "object"
+}Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds a scope (per-HSN) but no extra behavioral traits like rate limits, data coverage, or side effects. It does not contradict annotations, but also does not go beyond them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that immediately states the tool's purpose and contents. Every word earns its place, with no redundant fluff or repetition of schema details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool with one optional parameter, full schema coverage, clear annotations (read-only), and an existing output schema, the description provides enough context for an agent to select and invoke it correctly. No critical information is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with the 'period' parameter fully documented by an enum and default values. The description's phrase 'for a period' only repeats the schema concept without adding format, examples, or additional meaning. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb-phrase 'Per-HSN-code tax rollup' and lists concrete contents (taxable value, CGST/SGST/IGST/cess, invoice count). This clearly distinguishes it from sibling tools like get_gstr1_summary or get_state_wise_tax by focusing on HSN-level aggregation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for tax summaries by HSN code and a period, but it does not explicitly state when to choose this tool over alternatives such as get_tax_summary or get_gstr1_summary. No exclusions or alternative recommendations are provided, so guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct data points (e.g., get_analytics_summary vs get_brand_score). However, 'search' and 'search_catalog' have overlapping functionality and could cause confusion, and 'fetch' is a helper tied to 'search', adding minor ambiguity.
The majority use consistent verb_noun snake_case (e.g., get_inventory, list_stores). Exceptions like 'fetch' and 'search' (without object) break the pattern, but they are few.
43 tools is excessive for a data-retrieval-only API. Many get_* and search_* tools could be consolidated (e.g., search_catalog, search_inventory, search_orders are similar). The large number will overwhelm an agent.
The tool set is entirely read-only (get, search, list, fetch). There are no create, update, or delete tools, which is a critical gap for managing e-commerce operations. Agents can only view data, not act on it.