Skip to main content
Glama
tearsheet

tearsheet

by kewonit

reconcile_figure

Read-only

Verify a quarterly Tijori figure for revenue, profit before tax or net profit against the company's own XBRL filing, returning both values in crore and a matched, mismatch or unchecked status.

Instructions

Check a quarterly figure from Tijori against the company's own filing.

    metric is revenue, profit_before_tax or net_profit, and period is a
    quarter such as "Sep 2026". Needs that quarter's XBRL results filing in
    the filings folder. Returns both figures in crore and their difference.
    The verification status says matched, mismatch or unchecked, with the
    reason.
    

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": {
      "company": "<company>",
      "metric": "<metric>",
      "period": "<period>"
    },
    "name": "reconcile_figure"
  }
}

Input Schema

NameRequiredDescriptionDefault
basisNoconsolidated
metricYes
periodYes
companyYes

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofNo
unitsNo
entityNo
sourcesNo
warningsNo
next_cursorNo
retrieved_atNo
verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries the rest and does so well: it discloses the prerequisite filing dependency, the units of the returned figures (crore), and the three-state verification outcome with a reason. It stops short of saying whether a mismatch is an error or a normal result, which would fully close the loop.

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 core purpose is front-loaded in the first sentence and the remaining lines are dense with useful facts. Minor waste in the trailing sentence about verification status, and the odd line-wrapping, keep it from a 5.

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 read-only reconciliation tool with an output schema, the description covers purpose, prerequisite data, units and outcome states — enough to call it correctly. The one meaningful gap is the unexplained basis parameter, whose default could silently change the result.

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 coverage is 0%, so the description must compensate. It adds real meaning for metric (enumerating the three allowed values) and period (format example "Sep 2026"), but company and especially basis (consolidated vs standalone, defaulting to consolidated) receive no explanation at all.

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 opens with a specific verb and resource: check a quarterly figure from Tijori against the company's own filing. That cross-verification purpose is clearly distinct from retrieval siblings like get_financials or company_snapshot, so an agent can route without opening the schema.

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?

It states a real precondition — that quarter's XBRL results filing must exist in the filings folder — which implies when the tool is applicable. However, it never says when to prefer this over get_financials or read_filing, nor what to do when no filing is present beyond the 'unchecked' status.

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