[Global Equities Screener] Screen Singapore Exchange (SGX) — STI components and SE-Asia REIT universe.
Args: criteria: filter dict (sector, market cap, dividend yield, etc.) limit: max rows to return
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| criteria | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe, read-only operation. The description adds no new behavioral traits (e.g., rate limits, data freshness, or side effects). It merely restates the scope without enhancing transparency beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, with a single purpose line and two bullet-pointed parameter explanations. Every sentence adds value, and there is no redundancy or unnecessary detail. It is well-structured and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lacks information about the output format (e.g., list of tickers, full data rows). While the parameters are explained, the criteria dictionary's possible keys are only hinted at. For a tool with no output schema, more detail on return values would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds meaning to the parameters by explaining that 'criteria' is a filter dict for sector, market cap, etc., and that 'limit' sets max rows. Since the schema has 0% description coverage, this is helpful but vague ('etc.'). It does not provide specific valid keys or value formats for criteria.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool screens the Singapore Exchange (SGX) for STI components and SE-Asia REIT universe. It uses a specific verb ('Screen') and identifies the resource (SGX). However, it does not explicitly describe what the tool returns (e.g., a list of stocks with details), which slightly reduces clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The tool name and description imply it is for Singapore stocks. The sibling tools include many other country-specific screeners, so an agent can infer when to use this one. However, there is no explicit guidance on when not to use it or alternatives for different regions, leaving some ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.