Taokeh MCP server

Income statement

income_statement

Read-only

Your profit and loss for a period: revenue, cost of goods sold, gross profit, expenses and net income. COMPARISON (optional): to answer "how does this month compare with last?" ask for it here — NEVER call this tool twice and subtract the figures yourself. Set compare to 'previous_period' (the window of EQUAL LENGTH immediately before this one) or 'same_period_last_year' (the same dates one year earlier), OR give an explicit earlier window with BOTH compareFrom and compareEnd. You get both periods' full statements plus, for every account line and every total, deltaCents and deltaPct computed server-side in integer cents. deltaPct is NULL whenever the earlier figure is zero — a percentage change from zero is undefined, so report it as "no comparable base", never as ∞% or 100%. Percentages are measured against the ABSOLUTE earlier figure, so a movement out of a loss keeps the sign of the movement. windows states both windows, each one's day count, whether they are the same length, and whether either is still open (running to today or beyond, so its figures can still move); notes says all of this in plain words. READ notes BEFORE quoting a variance: if equalLength is false you are looking at a partial period against a full one and must say so.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes
`from`	Yes
`compare`	No	Named comparison window. 'previous_period' = the equal-length window immediately before from…to; 'same_period_last_year' = the same dates one year earlier. Omit for no comparison.
`compareEnd`	No	End of an explicit comparison window (use WITH compareFrom).
`compareFrom`	No	Start of an explicit comparison window (use WITH compareEnd; overrides `compare`).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedAug 18, 2026

addedInput schema / properties / compare

Added value: +{
+  "description": "Named comparison window. 'previous_period' = the equal-length window immediately before from…to; 'same_period_last_year' = the same dates one year earlier. Omit for no comparison.",
+  "enum": [
+    "previous_period",
+    "same_period_last_year"
+  ],
+  "type": "string"
+}

addedInput schema / properties / compareEnd

Added value: +{
+  "description": "End of an explicit comparison window (use WITH compareFrom).",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / compareFrom

Added value: +{
+  "description": "Start of an explicit comparison window (use WITH compareEnd; overrides `compare`).",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

First observedAug 9, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already indicate read-only, but the description adds substantial behavioral context beyond that: it explains that comparison returns deltaCents and deltaPct computed server-side, details about deltaPct being NULL when the earlier figure is zero, how percentages are measured, and the structure of the `windows` and `notes` fields. No contradictions with annotations.

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 front-loaded with the core purpose in the first sentence. Every subsequent sentence earns its place by explaining comparison behavior, return fields, and edge cases. Despite being longer, the structure is logical and all content is necessary for correct tool usage.

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

Completeness5/5

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

Given 5 parameters (2 required), no output schema, and moderate complexity, the description provides complete coverage. It explains the output structure (deltaCents, deltaPct, windows, notes), handles edge cases (NULL deltaPct, unequal window lengths), and gives usage instructions. No gaps are apparent.

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

Parameters5/5

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

Despite 60% schema description coverage, the description adds significant meaning to all five parameters. It explains the purpose of `from` and `to` as the primary period, details the `compare` enum options with clear definitions, and explicitly states that `compareFrom`/`compareEnd` must be used together and override `compare`. This fully compensates for schema gaps.

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 it provides profit and loss for a period, listing major line items (revenue, COGS, gross profit, expenses, net income). This distinguishes it from sibling tools like balance_sheet or cash_forecast by specifying the exact financial statement. The verb 'your profit and loss' is specific and the resource is well-defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the comparison feature and, crucially, tells the agent NEVER to call the tool twice and subtract manually. It provides clear instructions on setting the `compare` parameter or using explicit `compareFrom`/`compareEnd`. It also warns to read `notes` before quoting a variance and explains how to handle unequal length windows.

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

All Taokeh MCP server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?