schedule-iii

Save statement settings

save_statement_settings

Destructive

Save statement settings (rounding unit, signatory details, company information used on the statement face).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cin`	Yes
`client_id`	Yes	The entity (client) id — from list_clients.
`font_name`	No		Calibri
`period_id`	Yes
`unit_label`	Yes
`include_cfs`	No
`template_id`	Yes
`entity_class`	No
`rounding_off`	No	Whole-unit value rounding. When true (the default), every figure is rounded to the presentation unit and each CA-read total (profit, total assets, equity and liabilities) equals the rounded exact figure. A computed "Rounding off" line under Other expenses is only the profit adjustment; remaining Balance-Sheet rounding is disclosed under reserves / other current assets. false renders exact two-decimal figures.
`unit_divisor`	Yes
`equity_face_value`	Yes
`registered_office`	Yes
`suppress_nil_lines`	No
`entity_name_override`	Yes
`weighted_equity_shares`	Yes
`weighted_equity_shares_py`	Yes
`weighted_potential_equity_shares`	Yes	Weighted average potential equity shares (dilutive — options, convertibles). ADDITIONAL shares from options/convertibles only — not the total diluted share count. Enter 0 if the company has none. Do not repeat the basic share count.
`weighted_potential_equity_shares_py`	Yes	Weighted average potential equity shares — previous year (dilutive). ADDITIONAL shares from options/convertibles only — not the total diluted share count. Enter 0 if the company has none. Do not repeat the basic share count.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / rounding_off / description

Previous value: -"Whole-rupee value rounding. When true (the default), every figure is rounded to the nearest rupee and the net rounding difference is posted as a computed \"Rounding off\" line under Other expenses so the balance sheet ties to the rupee. false renders exact two-decimal figures."New value: +"Whole-unit value rounding. When true (the default), every figure is rounded to the presentation unit and each CA-read total (profit, total assets, equity and liabilities) equals the rounded exact figure. A computed \"Rounding off\" line under Other expenses is only the profit adjustment; remaining Balance-Sheet rounding is disclosed under reserves / other current assets. false renders exact two-decimal figures."

Changed2 schema fields changedSep 20, 2026

addedInput schema / properties / weighted_potential_equity_shares / description

Added value: +"Weighted average potential equity shares (dilutive — options, convertibles). ADDITIONAL shares from options/convertibles only — not the total diluted share count. Enter 0 if the company has none. Do not repeat the basic share count."

addedInput schema / properties / weighted_potential_equity_shares_py / description

Added value: +"Weighted average potential equity shares — previous year (dilutive). ADDITIONAL shares from options/convertibles only — not the total diluted share count. Enter 0 if the company has none. Do not repeat the basic share count."

First observedAug 6, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds no behavioral detail beyond the word 'Save'. It does not mention that existing settings are overwritten, that many fields are required, or any side effects. There is no contradiction with annotations, but the description contributes little 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.

Conciseness4/5

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

The description is a single concise sentence with no filler and the key resource is front-loaded. Its brevity is a virtue, though it also contributes to the incompleteness penalized in other dimensions.

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?

For a destructive save operation with 18 parameters, 13 required, and no output schema, a one-sentence description is insufficient. It omits overwrite semantics, the significance of the required fields, and how this tool relates to statement finalisation or other save tools.

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

Parameters2/5

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

Schema description coverage is only 22%, so the description should compensate by clarifying undocumented parameters. It only provides broad categories like 'rounding unit' and 'company information', leaving template_id, include_cfs, suppress_nil_lines, font_name, and the weighted share fields unexplained. The schema itself documents only four parameters, so this is a significant gap.

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?

The description uses a specific verb ('Save') and resource ('statement settings') and enumerates content categories (rounding unit, signatory details, company information). It distinguishes the tool from most sibling save_* tools by naming the statement-settings resource, though it does not explicitly differentiate from any particular sibling.

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 is given on when to use this tool versus related save_* siblings such as save_accounting_policies or save_disclosures, nor are prerequisites or preconditions mentioned. The only usage cue is implied by the purpose statement itself.

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

All schedule-iii tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?