Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_sustainability

Retrieve ESG and sustainability scores for a Yahoo Finance symbol such as AAPL via Crawlora MCP; returns empty esgScores when Yahoo has no data.

Instructions

Yahoo Finance sustainability. Returns ESG and sustainability scores for a Yahoo Finance symbol such as AAPL, under modules.esgScores. When Yahoo recognises the ticker but has no ESG data, esgScores comes back empty instead of an error.

Input Schema

NameRequiredDescriptionDefault
symbolYesYahoo Finance symbol such as AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and it delivers a valuable trait beyond the schema: a recognized ticker with no ESG data returns an empty `esgScores` rather than an error. It also names the response location (`modules.esgScores`). It omits auth/rate-limit context, but the empty-result disclosure is the meaningful one for this tool.

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?

Three tight sentences, front-loaded with purpose, then response path, then the edge case. Each sentence earns its place, though the opening 'Yahoo Finance sustainability.' fragment is slightly redundant with the following clause.

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 single-parameter read tool with no output schema, the description covers the purpose, the response location, and the important empty-result behavior. Nothing critical is missing, though it could note whether the result is cached or how often ESG scores update.

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 symbol parameter is already documented. The description repeats the AAPL example already present in the schema and adds no syntax or format detail beyond it, so the baseline 3 applies.

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 ESG and sustainability scores') and names the input symbol format. It clearly distinguishes itself from the many sibling yahoo_finance_ticker_* tools (quote, valuation, dividends, etc.) as the ESG-specific one.

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?

Usage is only implied: an agent can infer you call this to get ESG data, but there is no explicit when-to-use, no when-not-to-use, and no routing to alternatives such as yahoo_finance_ticker_valuation. The edge-case note is behavioral, not usage guidance.

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