Skip to main content
Glama

FinanceQuery

Sector Overview

get_sector
Read-onlyIdempotent

Get comprehensive sector data (overview, performance, top companies, ETFs) for one of the 11 GICS sectors.

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": {
      "sector": "<sector>"
    },
    "name": "get_sector"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoTarget language for translated text fields (BCP 47, e.g. "ja", "zh-Hant"); English or omitted = no translation
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
sectorYesSector slug: technology|financial-services|consumer-cyclical|communication-services| healthcare|industrials|consumer-defensive|energy|basic-materials|real-estate|utilities

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already provide the safety profile: read-only, open-world, idempotent, and non-destructive. The description adds that the response bundles overview, performance, top companies, and ETFs, but it does not discuss error behavior, unknown sector handling, or response shape beyond listing categories.

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 definition is a single front-loaded sentence with no wasted wording. It efficiently states the resource, aggregate scope, included data categories, and valid domain.

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?

For a read-only aggregator with fully described parameters and no output schema, the description adequately names the bundled data categories and the GICS sector constraint. It could be stronger by clarifying how this aggregate view relates to specialized sector tools, but it is largely complete for correct invocation.

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 100%, so the sector slug, lang, and fields parameters are already documented in the schema. The description reinforces that the sector must be one of the 11 GICS sectors, but it does not add syntax or meaning beyond what the schema provides.

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 states a specific verb and resource: get comprehensive sector data for one of the 11 GICS sectors, and lists the main data categories included. It is clear in isolation, but it does not explicitly distinguish this aggregate sector view from focused siblings such as get_sector_performance or get_sector_pe.

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?

The word 'comprehensive' implies this is the broad sector-overview tool rather than a narrow metric tool, which gives an agent some implied usage context. However, it does not state when to choose this over specialized sector siblings 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.