Skip to main content
Glama

FinanceQuery

Sector P/E Ratios

get_sector_pe
Read-onlyIdempotent

Get price/earnings ratios by market sector, provider-routed (Yahoo screener fan-out, keyless).

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

Input Schema

NameRequiredDescriptionDefault
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.4/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, open-world behavior, so the description just needs to add context. It does: 'keyless' tells the agent no credentials are needed, and 'Yahoo screener fan-out' signals the data is sourced from multiple upstream screener calls, which implies aggregation. It does not mention latency or rate-limit implications of that fan-out, which keeps it out of the top band.

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 front-loaded sentence with no filler; the resource and scope come first. The parenthetical is dense jargon but is short and does not bury the main statement.

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

Completeness3/5

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

This is a simple one-parameter read tool with rich annotations, so not much is required, but with no output schema the description never indicates the return shape (e.g., per-sector P/E values keyed by sector name). An agent can call it, but cannot anticipate the response structure.

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?

The only parameter, 'fields', is fully documented in the schema (100% coverage) with its comma-separated format and default behavior. The description adds nothing about what fields are available or how they map to P/E output, so the schema carries the entire load and the baseline of 3 applies.

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 uses a specific verb and resource ('Get price/earnings ratios by market sector'), which is enough to separate it from ticker-level tools like get_ratios_ttm and from the broader screener. It stops short of explicitly naming a sibling to distinguish itself from, so it falls just below the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no reference to alternatives such as get_ratios_ttm or screener. The parenthetical about provider routing describes how it works internally, not when an agent should pick 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.