Skip to main content
Glama

Sector

sector
Read-onlyIdempotent

StockMap's read of one US sector or industry, by name (Information Technology, semiconductors, banks): its 2-week lean from the model's nightly calls, how its stocks' calls split, its industries, and its largest stocks with each one's call and move on the day. Use it when someone asks how a US sector or industry looks, or which of its stocks look strong or weak. Its card draws the sector's or industry's stocks as StockMap's heatmap, coloured by their move. Each answer carries the not-advice line and the run date.

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

Input Schema

NameRequiredDescriptionDefault
nameYesA US sector or industry by name: Information Technology, Health Care, semiconductors, banks, software

Output Schema

NameRequiredDescriptionDefault
runYes
queryYes
scopeNoNone when no one sector or industry matched
closestNoThe sectors and industries it may have meant
not_adviceNoThe model's track-recorded read, not financial advice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful behavioral context beyond that: the 2-week lean, the stock-call split, the heatmap card colored by move, the not-advice line, and the run date. It does not discuss rate limits or permissions, which keeps it from a 5.

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 is front-loaded with the tool's purpose and stays focused on what the result contains. It is somewhat dense with output details that the output schema may already cover, but every sentence still carries useful context and there is no obvious filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only lookup with an output schema and full annotation coverage, the description supplies everything an agent needs: scope (US sectors/industries), inputs, returned content, card behavior, and the not-advice/run-date caveats. No critical behavioral or selection detail is missing.

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 100% for the single required 'name' parameter, and the schema already provides examples (Information Technology, Health Care, semiconductors, banks, software). The description repeats similar examples (Information Technology, semiconductors, banks) but adds no new meaning such as accepted aliases, case sensitivity, or partial matching, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('StockMap's read of one US sector or industry, by name') and enumerates what the read returns: 2-week lean, calls split, industries, largest stocks with calls and day moves. It is clearly distinguishable from siblings like stock_call (single stock) or market_map (broader map) without opening a schema.

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?

It gives an explicit usage context: 'Use it when someone asks how a US sector or industry looks, or which of its stocks look strong or weak.' That is strong when-to-use guidance, but it does not name when-not-to-use cases or the sibling alternative (e.g., stock_call for a single name).

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.

Resources