Skip to main content
Glama

FinanceQuery

Market Summary

get_market_summary
Read-onlyIdempotent

Get market overview with major indices and currencies for a region.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>"
    },
    "name": "get_market_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoTarget language for translated text fields (BCP 47, e.g. "ja", "zh-Hant"); English or omitted = no translation
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
regionYesRegion code: US|GB|DE|CA|AU|FR|IN|CN|HK|BR|TW|SG (default: US)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety and side-effect profile is fully covered. The description only adds the content scope (indices and currencies per region); it says nothing about data freshness, caching, or how much is returned.

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?

A single front-loaded sentence with no filler, so nothing is wasted. It is arguably slightly too terse for the amount of behavior it leaves unexplained, but that is a completeness issue rather than verbosity.

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 only 3 parameters (1 required), full schema coverage and rich annotations, this is close to adequate. However, there is no output schema, so the description carries the burden of saying what a "market overview" actually returns, and "major indices and currencies" is only a hint.

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%, with region, lang and fields all documented in the schema including the region code list and default. The description adds no meaning beyond that, so the 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?

"Get market overview with major indices and currencies for a region" states a specific verb (get) and resource (market overview) plus the content scope (indices, currencies). It is distinguishable from narrow siblings like get_forex or get_index_constituents, though it does not name them.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives. At best the phrase "market overview" implies a broad, first-look query versus a single-asset tool, leaving the agent to infer that trade-off.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.