Skip to main content
Glama
tearsheet

tearsheet

by kewonit

get_operating_metrics

Read-only

Retrieve a company's operating metrics, such as capacity, volumes, or deal wins, and filter by metric name to inspect company-specific KPIs beyond financial statements.

Instructions

Get a company's operating metrics, such as capacity, volumes or deal wins.

These are company-specific KPIs beyond the financial statements. Many smaller companies have none, which returns an empty list. Use metric to filter by part of a name. Each metric has its own unit. With Tijori's free plan only the latest value is available, matching what Tijori's own pages show, and history needs a paid plan.

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>"
    },
    "name": "get_operating_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
metricNo
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 most of the burden and does so well: it discloses that missing data yields an empty list rather than an error, that each metric has its own unit, and that history is gated behind a paid plan while free tier returns only the latest value. Pagination behavior of limit is not discussed.

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?

Front-loaded with the core purpose, followed by caveats in a logical order; no filler sentences. Slightly rambling list of caveats, but every sentence carries information.

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?

An output schema exists, so return-value explanation is unnecessary, and the tier limitations plus empty-result behavior give enough to call correctly. The gaps are the undocumented limit parameter and company input format.

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 description coverage is 0%, so the description must compensate. It clarifies that metric matches by part of a name (substring semantics beyond the plain string type), but leaves company's format and limit's role, default and 20-record ceiling undocumented.

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 a specific verb and resource ("Get a company's operating metrics") and grounds it with concrete examples (capacity, volumes, deal wins). The phrase "beyond the financial statements" implicitly separates it from the get_financials sibling, but no sibling is named explicitly.

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

Usage Guidelines4/5

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

Explains the context where this applies (company-specific KPIs not covered by financial statements) and warns that many smaller companies return an empty list, which helps an agent decide whether to call it. It stops short of naming an alternative tool to use instead when the caller actually wants financials.

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