Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_related

Find Google Finance related instruments for a quote such as AAPL:NASDAQ and return each item's ticker, exchange, name, price, change, percent change, and previous close.

Instructions

Google Finance related instruments. Returns the instruments Google Finance lists as related to a quote such as AAPL:NASDAQ. The response gives the queried instrument and an items list, each with ticker, exchange, name, price, change and change percent, and previous close.

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
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. It describes the response shape in detail (instrument plus items with ticker, exchange, name, price, change, change percent, previous close), which discloses output behavior. It does not state the operation is read-only, whether it requires any auth, or rate/coverage limits.

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 sentences, front-loaded with what the tool does and then the return contract. No filler; each clause earns its place.

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 purpose, identifier format, and the full return shape, which is what an agent needs to call and interpret it. It lacks only explicit read-only safety framing and alternative routing.

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 fully documented in the schema. The description only echoes the same example identifier format (AAPL:NASDAQ) without adding new meaning. Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb and resource: it returns the instruments Google Finance lists as related to a quote. This is a distinguishable capability vs. quote or search siblings. However, it doesn't explicitly name or contrast with the closest siblings (e.g. google_finance_quote, google_finance_search), so it stops short of full sibling differentiation.

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 implied by the purpose (look up instruments related to a given quote), and the quote example gives a concrete entry point. There is no explicit when-to-use guidance, no when-not-to-use, and no mention of alternatives such as google_finance_quote or google_finance_search.

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