Skip to main content
Glama
tearsheet

tearsheet

by kewonit

get_sector_view

Read-only

Retrieve market indices, sector indices, or conglomerate groups with price changes across periods, or fetch a named sector or group’s constituent companies and weights.

Instructions

Get market indices, Tijori's sector indices or conglomerate groups.

    Without a name, lists them with their price changes over periods such
    as 1D, 1M and 1YR*. With a name, such as "Private Bank" or "Adani",
    also returns that sector's or group's constituent companies and their
    weights. Tijori marks some periods with an asterisk and doesn't say
    what it means, so mention that when quoting them.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sector_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNosectors
nameNo
limitNo

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value by disclosing that name-mode returns constituent weights and that Tijori's asterisked periods are undefined and should be flagged when quoted, but it says nothing about pagination or how limit truncates the listing.

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 purpose, then behavior mode-by-mode, with no filler sentences. The asterisk caveat is useful but reads as an aside wedged into the final sentence.

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 shape needn't be described, and the description covers both invocation modes adequately. The main remaining hole is the limit parameter and default kind behavior for a zero-required-parameter tool.

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 carry the parameter burden. It explains the semantics of name well (missing vs. supplied changes the whole result shape) and alludes to the three kinds, but never mentions limit or how kind interacts with the listing, leaving a real gap against 0% coverage.

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?

Names a specific verb and resource set: market indices, Tijori sector indices, and conglomerate groups, which clearly separates it from company-level siblings like get_financials or get_ownership. It never explicitly contrasts itself with any sibling tool, so it lands at clear-but-undifferentiated rather than 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 Guidelines4/5

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

Gives explicit operational context for the two modes: call without a name to list and compare price changes, call with a name to drill into constituents and weights. It does not say when another tool would be preferable (e.g. find_company for a single stock) or when not to use it.

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