Skip to main content
Glama

FinanceQuery

Sector Performance History

get_sector_performance_history
Read-onlyIdempotent

Get sector performance per session, most recent first.

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_performance_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoSessions to return; omitted = 30
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuine behavioral fact: results come back most recent first. It says nothing about pagination, whether sectors are aggregated or listed, or what a 'session' is.

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?

A single short sentence with the resource statement front-loaded and the ordering fact appended; no filler. It borders on under-specified rather than padded, so it is efficient but leaves little for an agent to work with.

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

Completeness2/5

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

There is no output schema, so the description should explain what a record contains, but 'performance per session' is undefined (return percentages? price change? ranking?) and 'session' is unqualified. For a series-returning tool with no output schema, the description leaves the agent guessing about the result shape.

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 both parameters (limit with default 30, fields as a comma-separated GraphQL field list) are fully documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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?

Specific verb and resource ('Get sector performance'), plus a scope qualifier ('per session') and ordering ('most recent first'). It does not explicitly distinguish itself from the sibling get_sector_performance, so an agent must infer that this one is the time-series variant from the name alone.

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?

No explicit when-to-use or when-not-to-use guidance and no named alternative. The implied usage (retrieve a historical series of sector performance) is clear enough from 'history' and 'per session', but an agent comparing against get_sector_performance gets no routing help.

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.