Skip to main content
Glama
tearsheet

tearsheet

by kewonit

get_business_mix

Read-only

Retrieve a company's revenue splits by product, geography, or segment, plus market-share figures with as-of dates, to analyze its business mix and competitive position.

Instructions

Get how a company's business splits, and its market shares.

Returns the latest revenue split by product, geography, segment or other breakdowns Tijori tracks, each in percent, plus market share figures. Every market share has its own as-of date, and some are years old, so always check it. History of the revenue split and of market shares needs a paid Tijori 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_business_mix"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely non-obvious behavior: values are in percent, each market share carries its own as-of date and may be years stale, and historical depth is paywalled. It stops short of covering edge cases such as an unresolvable company name or empty result sets.

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 output description is front-loaded in the first sentence and the caveats follow in order of operational importance. A little is repeated between the opening line and the 'Returns the latest revenue split' sentence, but nothing is padding.

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?

With one read-only parameter and an output schema present, the definition needn't describe return structure, and it nevertheless flags units, staleness, and plan gating. The remaining hole is input format for 'company', which matters 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 description coverage is 0% for the single 'company' parameter, so the description carries the full burden. It only implies a company is supplied ('a company's business splits') and never says whether that is a ticker, legal name, or Tijori ID, or how it relates to find_company.

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: it returns a company's revenue split by product/geography/segment plus market share figures. That content is clearly distinct from get_financials or get_operating_metrics, but the description never names an alternative, so the agent must infer the boundary itself.

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 gives a concrete in-task instruction ('always check' the as-of date) and a gating condition (history requires a paid plan), which is real usage guidance. It does not say when to prefer this over get_financials or get_operating_metrics, so selection between siblings is left implicit.

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