Skip to main content
Glama
Sign In
PNPC-MCP-Tally-Prime

PNPC-MCP-Tally-Prime

by lokesh-sparrow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_stock_summary

Read-only

Retrieve the Stock Summary report from TallyPrime as of a specified date to review inventory positions. Provide the as-of date in DD-MM-YYYY format.

Instructions

Get the Stock Summary report from TallyPrime as of a given date

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": {
      "asOf": "<asOf>"
    },
    "name": "get_stock_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfYesAs-of date in DD-MM-YYYY format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, indicating it is a safe read operation. The description adds the date constraint but does not disclose additional behavioral traits such as the format of the report, whether it includes all stock items, or any limitations. With annotations covering the safety profile, a score of 3 is appropriate.

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?

The description is a single sentence that is front-loaded with the key action and resource. Every word is necessary, and there is no extraneous information.

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?

Given the tool's simplicity (one parameter, no output schema), the description is minimally adequate. However, it does not explain what the stock summary report contains (e.g., quantities, values) or any return format. For a tool with no output schema, a bit more detail would improve completeness, but it is not severely lacking.

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

Parameters3/5

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

Schema description coverage is 100% (the 'asOf' parameter includes format and constraints). The description's phrase 'as of a given date' aligns with the schema but adds no extra meaning beyond what is already in the schema. Baseline 3 is correct.

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 the verb 'Get', the resource 'Stock Summary report', and the constraint 'as of a given date'. This effectively distinguishes it from sibling tools like get_stock_items (individual items) and other financial reports.

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

Usage Guidelines3/5

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

The description implies usage when a stock summary report for a specific date is needed, but it does not explicitly state when to use this tool over alternatives (e.g., get_stock_items for item-level details) or when not to use it. No exclusions or prerequisites are mentioned.

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