Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

google_finance_markets_earnings

Retrieve Google Finance earnings calendar data with company names, fiscal periods, event times, conference call details, and ticker prices.

Instructions

Google Finance earnings calendar. Returns the Google Finance earnings calendar. Each item has the company name, fiscal period, event time (including a Unix timestamp), conference call phone and URL when listed, and the instrument with its ticker, exchange, price and change.

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully enumerates returned fields (company name, fiscal period, event timestamp, call details, instrument quote), which is helpful output transparency for a read-only tool. However, it omits scope details such as whether the calendar covers upcoming events only, timezone handling, pagination, or update frequency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are redundant: 'Google Finance earnings calendar' is immediately restated as 'Returns the Google Finance earnings calendar.' The field list that follows is front-loaded after that waste. The overall size is reasonable, but the repetition costs efficiency.

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?

With no output schema, the description does explain the structure of returned items, which is necessary and valuable. Yet it leaves a material gap: it never clarifies the calendar's time window (upcoming only? current day? all announced?), which an agent needs in order to decide whether this tool is appropriate. The description is adequate but incomplete for an earnings calendar tool.

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?

The tool has zero parameters, and the rubric sets a baseline of 4 for zero-parameter tools with full schema coverage. There is no parameter information to add, so the description appropriately does not discuss inputs.

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 earnings calendar'), so an agent can tell what the tool does. It distinguishes itself from generic calendar tools by naming Google Finance, but does not reference sibling alternatives such as yahoo_finance_ticker_earnings or yahoo_finance_calendar_results.

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?

The description offers no guidance on when to choose this tool versus related earnings or calendar tools. It says only what data is returned, with no usage context, prerequisites, or exclusions.

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