Browse industry verticals; sort by provider/API count.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Free text matched against name and description, e.g. "payments". | |
| page | No | Page number, 1-based (default 1). | |
| sort | No | Order: name, api_count, provider_count or composite, e.g. "provider_count". | |
| limit | No | Results per page, 1-100 (default 25). | |
| context | No | Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong. |
Changes observed during successful MCP inspections.
Input schema / properties / context / descriptionPrevious value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."Input schema / properties / page / descriptionPrevious value: -"Page number, 1-based (default 1). Use with `limit` to walk a long list."New value: +"Page number, 1-based (default 1)."Input schema / properties / limit / descriptionAdded value: +"Results per page, 1-100 (default 25)."Input schema / properties / page / descriptionAdded value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."Input schema / properties / q / descriptionAdded value: +"Free text matched against name and description, e.g. \"payments\"."Input schema / properties / sort / descriptionAdded value: +"Order: name, api_count, provider_count or composite, e.g. \"provider_count\"."Input schema / properties / contextAdded value: +{
+ "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only that results can be sorted, which is already exposed by the schema's sort parameter; it says nothing about pagination behavior, total counts, or result shape for a 5-parameter listing tool.
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?
A single short clause, front-loaded with the verb and resource plus the sort hook. Nothing is wasted, though the extreme brevity edges toward under-specification rather than pure conciseness.
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?
For a zero-required-parameter discovery tool with no output schema, the description is minimally adequate but omits what a browse call returns and how it relates to the industry detail/leader tools. It is complete enough to invoke, not to use optimally.
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% (q, page, sort, limit, context all documented), so the schema carries parameter semantics. The description merely restates the sort dimension ('provider/API count') and adds no format, default, or interaction detail beyond it. Baseline 3 applies.
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?
States a specific verb and resource: 'Browse industry verticals'. The sort capability is also mentioned, so an agent knows this is a listing/discovery call rather than a detail lookup. It does not, however, name any sibling (e.g. get_industry, find_apis, insights_industries) to disambiguate.
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?
There is no statement of when to use this tool versus alternatives such as get_industry (single industry) or find_apis/find_providers (entities within an industry), nor any prerequisite or exclusion. Usage is only implied by the word 'browse'.
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.