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

PNPC-MCP-Tally-Prime

by lokesh-sparrow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_cost_centres

Read-only

Retrieve all cost centres from TallyPrime to support cost tracking, allocation, and financial reporting via the PNPC-MCP-Tally-Prime MCP server.

Instructions

Get all cost centres from TallyPrime

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": "get_cost_centres"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true and openWorldHint=false. Description adds no contradiction and is consistent. It does not elaborate further but is adequate given annotations.

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?

Single, concise sentence. Front-loaded with action. No wasted words, though could be slightly more informative.

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?

With many sibling tools and no output schema, the description is minimal but works for a simple zero-param retrieval tool. Lacks detail on return structure, but annotations partially compensate.

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 has zero parameters with 100% description coverage, so baseline is 4. Description adds no extra parameter info but is not needed.

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

Purpose4/5

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

States verb 'Get' and resource 'all cost centres from TallyPrime' clearly. However, it does not distinguish from sibling tools like get_groups or get_ledgers which also retrieve master data from TallyPrime.

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 vs alternatives like get_groups. No mention of scope or prerequisites.

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