Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_company

Retrieve company profiles and stock metrics from Google Finance using a quote like AAPL:NASDAQ. Get CEO, sector, market cap, P/E ratio, price ranges, and volume.

Instructions

Google Finance company data. Returns Google Finance company details for a quote such as AAPL:NASDAQ: description, CEO, employee count, headquarters, sector, market capitalisation, P/E ratio, open, day high and low, 52-week high and low, and volume.

Input Schema

NameRequiredDescriptionDefault
quoteYesQuote identifier such as AAPL:NASDAQ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully compensates for the missing output schema by enumerating the returned fields, and 'Returns' implies a read-only operation, but it says nothing about permissions, rate limits, error behaviour on an invalid ticker, or data freshness.

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?

Two sentences, front-loaded with the tool's identity followed by the payload list; nothing is wasted. The opening fragment 'Google Finance company data.' is mildly redundant with the sentence that follows, keeping it just short of a 5.

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 and no annotations, the description covers what the agent most needs: the identifier format and the full set of returned fields. Only edge-case behaviour (bad ticker, missing company data) is left unspecified.

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% and the single `quote` parameter is documented in the schema; the description repeats the same example ('AAPL:NASDAQ') without adding format nuance such as exchange-suffix rules or accepted alternatives. Baseline 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 states a specific verb ('Returns') and resource ('Google Finance company details') and enumerates the payload (CEO, employee count, HQ, sector, market cap, P/E, OHLC, 52-week range, volume), so the agent knows exactly what comes back. It does not, however, distinguish itself from near-neighbours such as google_finance_quote or google_finance_financials, which overlap on price fields.

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, when-not-to-use, or alternative-tool guidance. The field list implies 'use this for company profile data', but with ~40 google_finance_* siblings the agent gets no explicit routing rule, which is exactly where guidance is most needed.

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