Screen Bolsa Mexicana de Valores (BMV) — IPC components and broader Mexican universe.
Args: criteria: filter dict (sector, market cap, 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, so the description adds minimal behavioral context beyond mentioning the scope (IPC components and broader universe). 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 very concise with a clear front-loaded purpose and two parameter descriptions. Every sentence is informative without waste.
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 covers the tool's purpose and parameter usage adequately for a simple screening tool with no output schema. Could be slightly more specific about criteria keys, but 'sector, market cap, etc.' is sufficient.
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 coverage, the description provides brief but clear parameter explanations: 'criteria: filter dict (sector, market cap, etc.)' and 'limit: max rows to return'. This adds value beyond the raw schema types.
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 states 'Screen Bolsa Mexicana de Valores (BMV) — IPC components and broader Mexican universe', which is a specific verb and resource. It clearly distinguishes from sibling tools which target different countries.
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 description implies this tool is for Mexican equities, and sibling names make it obvious when to use other country screens. However, no explicit when-not or alternative guidance is provided.
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.