List active UAE and MENA VCs by funding stage and sector to help founders identify relevant investors.
List active UAE / MENA VCs by stage and sector.
| Name | Required | Description | Default |
|---|---|---|---|
| stage | No | Optional stage focus, one of: pre_seed, seed, series_a, series_b, growth. | |
| sector | No | Optional sector substring (e.g., "fintech", "saas"). |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds only the useful scope qualifier that it lists 'active' VCs, without explaining result shape, filtering behavior, or pagination; this is adequate but limited given the annotation coverage.
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 definition is a single front-loaded sentence with no wasted words. It communicates the resource and the two filter dimensions immediately.
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 the simple read-only nature, full schema descriptions, annotations, and an output schema, the description is largely sufficient for correct invocation. Its main omission is routing guidance versus similar discovery tools, which is reflected in the usage dimension.
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?
Schema description coverage is 100%, with both optional parameters clearly documented. The description restates that filtering is available 'by stage and sector,' but adds no syntax, format, or edge-case guidance beyond what the schema already provides.
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 gives a specific verb and resource: 'List active UAE / MENA VCs' with filtering by stage and sector. It is clear what the tool does, though it does not explicitly distinguish itself from nearby tools such as accelerator_search or grant_programs.
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?
It implies the tool is used to list VCs, but provides no explicit when-to-use guidance, prerequisites, or alternatives. There is no statement about when to use this versus accelerator_search or other discovery tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.