The niche explorer: every niche reported, with its headline numbers. Free. Same as GET /v1/niches.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_niches"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| api_key | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden; it does disclose two useful traits — the operation is free and behaves like a GET (read-only) endpoint. It says nothing about pagination/truncation despite a limit cap of 200, nor about what happens when api_key is absent, which are real behavioral gaps for an unannotated 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?
Three short fragments, zero filler, and the core purpose is front-loaded. The telegraphic style ("Free. Same as GET /v1/niches.") is efficient but sacrifices clarity it could have spent a few more words on.
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?
An output schema exists, so return values need no explanation, and there are only two simple parameters. What remains missing is minor but real: the limit/pagination contract and any key requirement. For a simple free listing endpoint, this is close to complete.
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 0%, so the description must compensate, and it does not: neither `limit` (1–200, default 50) nor `api_key` is mentioned. The reader learns nothing about what limit controls or whether the key is required for the free tier.
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 niche explorer: every niche reported, with its headline numbers" clearly identifies the resource (niches) and that it's an enumeration with summary stats, and the GET /v1/niches reference anchors it to a known read operation. It hints at a distinction from the sibling niche_report (all niches with headlines vs. a single report), but never states that boundary explicitly.
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?
"Free" is a genuine selection signal (cost), and "every niche" implies the browse-all use case. However, there is no explicit when-to-use vs. the sibling niche_report, no mention of when to prefer a targeted report, and no exclusions or prerequisites.
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.