Skip to main content
Glama

enterprise-mcp-gateway

global-equities-screener__screen_indonesia_idx

Read-only

[Global Equities Screener] Screen Indonesia Stock Exchange (IDX) — LQ45, IDX30, full Jakarta board.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
criteriaNo

TDQS

A4/5.0
Behavior3/5

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

Annotations provide readOnlyHint=true, so the safety profile is covered. The description adds that it screens specific boards but does not disclose return format, pagination, or any side effects. With annotations, the description adds modest behavioral context.

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 extremely concise: two lines plus a brief args list. Every sentence is necessary and front-loaded with the target market and boards. No wasted words.

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?

The tool is a simple screener with no output schema. The description covers purpose and parameters adequately. However, it lacks details on return format, how to construct criteria, and any limitations. For its simplicity, it is nearly complete.

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?

Schema description coverage is 0%, so the description must compensate. It explains 'criteria' as a filter dict (sector, market cap, etc.) and 'limit' as max rows. This adds meaning beyond the raw schema types, though 'etc.' is vague and field names are not explicit.

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?

The description clearly states it screens the Indonesia Stock Exchange (IDX), listing specific boards (LQ45, IDX30, full Jakarta board). The verb 'Screen' is appropriate. It distinguishes from sibling tools which target other exchanges.

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?

The description does not provide explicit when-to-use or when-not-to-use guidance. It is clear that it should be used for Indonesian equities, but no alternatives or exclusions are mentioned (e.g., vs finance__screen_stocks). The context is implicit but lacking explicit guidelines.

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

B3.2/5.0
Disambiguation2/5

Many tools have overlapping functionality across categories (e.g., multiple search_arxiv, search_google_scholar, real estate tools, DNS/WHOIS checks). An agent would struggle to differentiate between similar tools from different categories, leading to ambiguity.

Naming Consistency3/5

Tools follow a 'category__verb_noun' pattern mostly, but verbs vary (get, search, screen, check, etc.) and some categories use different orders (e.g., 'get_repo_stats' vs 'search_repos'). The consistency is acceptable but not uniform across the entire set.

Tool Count2/5

With 152 tools, the server is excessively large for a single MCP server. While it aims to be an all-in-one gateway, the sheer number overwhelms the agent and likely exceeds practical limits for coherent selection.

Completeness3/5

The server covers a wide range of domains (finance, real estate, news, developer tools, etc.) but has notable gaps (e.g., social media APIs, CRM tools). Coverage is broad but not exhaustive, and some niche areas (e.g., global stock exchanges) are over-represented.

Resources