Skip to main content
Glama
Sign In
tally-mcp-server

tally-mcp-server

by visheshStallion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_stock_item

Retrieve details for a stock item by entering its exact name as stored in Tally. Returns precise inventory information for a single item.

Instructions

Get details for a single stock item by exact name.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact stock item name as it appears in Tally.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get details' without specifying what details are returned, how exact matching behaves, or what happens when the item is not found. This is a minimal transparency gap for a read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single clear sentence that front-loads the resource and scope. It is appropriately sized for a simple tool, with no redundant wording.

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

Completeness2/5

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

Given there is no output schema, the description's vague 'details' leaves the return shape uncertain, and it does not clarify error behavior or how this tool relates to list_stock_items. For a tool with minimal documentation, this leaves an agent guessing about the response.

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 schema already documents the 'name' parameter well, and the description reinforces the 'exact' requirement. Since schema coverage is 100%, the description adds marginal semantic value beyond restating the existing parameter description.

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 uses a specific verb ('Get') and resource ('single stock item') with an explicit scoping constraint ('by exact name'). This clearly distinguishes it from the sibling list_stock_items, which retrieves multiple items.

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 'by exact name' phrasing implies this tool is for looking up one known item, but it does not explicitly state when to prefer list_stock_items or what to do if the exact name is unknown. The guidance is present only implicitly.

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