Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_sector

Fetch sector details by key to get overview, top companies, ETFs, mutual funds, industries, and research reports. Use the sectors endpoint for valid keys.

Instructions

Yahoo Finance sector detail. Returns Yahoo Finance detail for one sector key such as technology: name, overview, top companies, top ETFs, top mutual funds, the sector's industries and research reports. Valid keys come from /yahoo-finance/sectors.

Input Schema

NameRequiredDescriptionDefault
keyYesSector key such as technology

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the disclosure burden and does so by enumerating the returned fields, signaling this is a read-only, single-sector detail lookup. It does not mention auth, rate limits, or pagination, but for a simple keyed lookup the payload description is the behavior an agent most needs.

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?

Two tight sentences: purpose/payload first, key provenance second. No filler, and the most decision-relevant information is front-loaded.

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?

No output schema exists, yet the description enumerates the returned fields and tells the agent where valid keys originate, closing both the input and output gaps. Sufficient for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the inline parameter description already documents the `key` field, so baseline is 3. The description adds meaning by giving a concrete example ('technology') and pointing to '/yahoo-finance/sectors' as the authoritative source of valid keys, going beyond the schema.

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?

States a specific verb and resource ('Returns Yahoo Finance detail for one sector') and enumerates the exact payload: name, overview, top companies, top ETFs, top mutual funds, industries, and research reports. This clearly distinguishes it from the sibling sector-list tool.

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?

The description routes the agent to the companion tool by stating valid keys come from '/yahoo-finance/sectors', which tells the agent how to obtain a valid input. It stops short of an explicit 'use this tool when...' clause or a named alternative sibling, but the sourcing hint is strong usage context.

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

Deploy Server

Other Tools