tally-mcp-server

list_stock_items

Get inventory/stock items from the active Tally company with closing stock quantity and value. Use the name filter to locate specific items.

Instructions

List inventory/stock items in the active Tally company, including closing stock quantity and value.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_stock_items"
  }
}

Input Schema

Name	Required	Description	Default
`nameContains`	No	Only return stock items whose name contains this substring.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It correctly implies a read-only listing operation and adds useful context about the active company and returned fields. It does not mention permissions, pagination, or empty-result behavior, but for a simple list operation the core behavior is reasonably transparent.

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 one concise sentence with no filler. It front-loads the action and resource, then adds the key output information. Every word contributes value.

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

Completeness4/5

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

For a simple tool with one optional parameter and no output schema, the description covers the essential context: what is listed, where it is listed, and what relevant fields are returned. It could additionally clarify sorting or absence behavior, but those are minor gaps for this tool's complexity.

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?

The single optional parameter nameContains is already fully described in the input schema with 100% description coverage. The tool description adds no additional parameter-level detail, so the baseline score of 3 applies.

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 a specific action ('List'), a specific resource ('inventory/stock items'), and a scope ('active Tally company'). It also mentions the included output fields ('closing stock quantity and value'), distinguishing it from the singular sibling get_stock_item without confusion.

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 intended use is implied: call this to enumerate stock items in the active company. However, the description does not explicitly mention when to prefer this over alternatives such as get_stock_item, nor does it state exclusions or conditions. Some guidance is present, but it relies on inference.

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

Deploy Server