Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_classification

Retrieve Google Finance category labels and instrument details for a quote like AAPL:NASDAQ to classify stocks by sector and view price data.

Instructions

Google Finance classification data. Returns the category labels Google Finance assigns to a quote such as AAPL:NASDAQ, for example Technology, in categories. The response also carries the instrument itself: ticker, exchange, name, current price, change, previous close, currency and after-hours data.

Input Schema

NameRequiredDescriptionDefault
quoteYesQuote identifier such as AAPL:NASDAQ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the return contents, including `categories` and the embedded instrument fields. It does not mention errors, rate limits, or explicitly state read-only behavior, but it is transparent about output shape.

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?

The description is short, front-loaded with the primary purpose, and every sentence contributes useful information about the returned data.

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 simple one-parameter retrieval tool with no output schema, the description sufficiently enumerates the return values. It could be stronger by noting when this output overlaps with sibling quote tools, but it is otherwise complete.

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 schema coverage is 100% and already describes the `quote` parameter with an example. The description repeats the `AAPL:NASDAQ` example but adds no additional format or validation semantics beyond the schema.

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 clearly states a specific behavior: returning Google Finance category labels for a quote, with an example. It does not distinguish itself from sibling tools such as google_finance_quote or google_finance_ticker, which also return instrument data.

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?

It implies the tool is for classification data, but never says when to use it instead of alternatives like google_finance_quote or google_finance_context. No exclusions, prerequisites, or selection guidance are provided.

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