Skip to main content
Glama
danchev

openmarkets

by danchev

get_market_summary

Specify a market to retrieve its overall performance summary, including key metrics and indicators.

Instructions

Retrieve a summary of the overall market performance.

Returns: dict: Market summary data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNoDictionary of market summaries
Behavior2/5

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

No annotations exist, yet the description only says 'Retrieve a summary' and mentions return type. It does not disclose behavioral traits like data freshness, side effects, or access requirements.

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?

Minimal length, but missing critical details. It is front-loaded but too sparse to be effective; could be more concise if it included parameter hints.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the single required parameter and no annotations, the description is incomplete. It does not explain the 'market' parameter or the return structure, leaving the agent underinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter 'market' has no description, and schema coverage is 0%. The description adds no meaning beyond the schema's name and type; the agent cannot infer what values are valid.

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 the tool retrieves a market summary (verb+resource). However, it does not distinguish from siblings like get_market_status or get_industry_overview, which could cause confusion.

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?

No guidance on when to use this tool versus alternatives. The sibling list includes many market-related tools, but the description fails to specify context or selection criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danchev/openmarkets'

If you have feedback or need assistance with the MCP directory API, please join our Discord server