Skip to main content
Glama

company_history

Assess a company's recent financial trajectory: retrieves key metrics such as revenue, cash, and margin, with period-over-period changes, three-period trends, and warnings for repeated adverse moves.

Instructions

The company's headline figures lined up across every recorded window: revenue, net margin, cash, cost share, overdue receivables, top-customer share, cash conversion days, break-even margin of safety, hours short, tie-out differences and open actions, each with its latest value, the change on the previous window, its direction over the last three, and a warning when it has moved the wrong way three windows running. Assembled from the books, customer ledgers and derived documents already recorded for this bundle; a figure a window could not build is a gap, never a zero. Deterministic; read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nowNo
engineNo
operationNobuild
entity_refNo
project_idYes
bundle_jsonNo
payload_jsonNo{}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

B3.1/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it states the tool is deterministic and read-only, explains the data source (books, customer ledgers, derived documents for this bundle), and specifies that un-buildable windows are gaps, never zeros. It does not discuss auth, rate limits, or pagination, but for a read-only aggregator these are minor omissions.

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 packs a large amount of specific information into three sentences and front-loads the headline scope before the data-source caveat. The first sentence is a long enumeration, but every clause adds a distinct metric or behavior; no filler.

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?

Although an output schema exists and the description richly specifies the output and missing-data semantics, the tool has 7 parameters with zero schema documentation and no usage guidance versus a large field of sibling company_* tools. An agent would struggle to know how to set operation, engine, or entity_ref, making the definition incomplete for correct invocation.

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 coverage is 0% across 7 parameters, so the description must compensate, but it never names or explains project_id, now, engine, operation, entity_ref, bundle_json, or payload_json. Only indirect hints exist ('for this bundle' hints at bundle_json; 'recorded window' hints at temporal parameters), which is not enough to map values to fields.

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 enumerates a specific resource – the company's headline figures across recorded windows – and lists concrete metrics (revenue, net margin, cash, etc.) and value components (latest value, change, three-window direction, warning). It does not use an explicit verb like 'list' or 'retrieve', and it does not explicitly contrast with sibling tools, so it falls short of a 5.

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 about when to choose company_history over alternatives like company_books, company_tie_out, or company_revenue. The description implies it is a read-only historical snapshot via 'Deterministic; read-only', but it never states the intended condition for use or any exclusions.

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