Skip to main content
Glama

global-equities-screener-mcp

screen_germany_dax

Read-only

Screen Xetra / Deutsche Börse — DAX 40, MDAX, SDAX, TecDAX.

Args: criteria: filter dict (sector, market cap, P/E, etc.) limit: max rows to return

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
criteriaNo

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, so no contradiction. Description adds that it screens but lacks details on data freshness, pagination, or 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?

Extremely concise: one-line purpose followed by two argument descriptions, no wasted words.

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?

Lacks information about return format, pagination, or typical use cases; for a screening tool with no output schema, more context is needed.

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?

With 0% schema coverage, the description explains 'criteria' as a filter dict with examples (sector, market cap, P/E) and 'limit' as max rows, providing useful context beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool screens specific German indices (DAX 40, MDAX, SDAX, TecDAX) on Xetra/Deutsche Börse, distinguishing it from sibling tools for other markets.

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?

Implies usage for German market screening via the name and description, but provides no explicit guidance on when to use vs. siblings or when not to use.

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.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct geographic exchange, with no overlap in markets screened. The descriptions specify the exchange and indices, making it easy for an agent to select the correct tool for a given country.

Naming Consistency5/5

All tools follow the exact same naming pattern: 'screen_<country>_<exchange>' in snake_case, providing a clear and predictable structure. There are no deviations or mixed conventions.

Tool Count4/5

26 tools is on the high side, but appropriate for a global equities screener covering many countries. Each tool serves a distinct market, so the count is justified by the breadth of coverage.

Completeness4/5

The set covers most major global equity markets, including US, China, India, Japan, and many others. However, some notable markets like Russia or some European exchanges are missing, and there is no tool for screening ETFs or indices directly.

Resources