Screen Thailand Stock Exchange (SET) — SET50, SET100, full Thai 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, query-like operation. The description adds the market scope and parameter hints but does not elaborate on return format, pagination, or error behavior. No contradictions.
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 concise, with a front-loaded purpose and two clear lines for parameters. Every sentence adds value—no fluff or redundancy.
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?
Given 2 simple parameters, no output schema, and annotations indicating read-only open-world, the description covers the tool's purpose and parameter semantics sufficiently. It lacks explicit output format or behavior, but that is minor for a screening tool.
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?
With 0% schema description coverage, the description compensates by explaining the criteria parameter as 'filter dict (sector, market cap, dividend yield, etc.)' and limit as 'max rows to return'. This adds meaning beyond the schema's type-only definitions.
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 the tool screens the Thailand Stock Exchange (SET), specifying the verb 'Screen' and the resource 'Thailand Stock Exchange'. It distinguishes from siblings by naming the country and market indices (SET50, SET100, full universe).
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's name and description imply it should be used for Thai equities, and the sibling list shows country-specific screens. However, no explicit when-to-use or when-not-to-use guidance is given, nor alternatives beyond the sibling naming convention.
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.
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.
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.
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.
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.