Get approved sites in the llmsmap.ru catalog with llms.txt URLs, token counts, and metadata.
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_catalog"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of sites to return, capped at 50. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the full behavioral burden. It indicates a read-only operation and specifies return contents, but it does not disclose default result size, ordering, pagination, or the behavior when no limit is provided.
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 a single sentence with the action and resource front-loaded, and no redundant or filler wording. It efficiently conveys the essential purpose.
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 one-parameter list tool with a documented schema and no output schema, the description adequately states the resource and return contents. It could be slightly more complete by specifying default behavior and the relationship to search_catalog, but it is sufficient for basic invocation.
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%: the only parameter, limit, already has a description including the 50 cap. The tool description adds no parameter-level information, so the baseline score of 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?
The description uses a specific verb ('Get') and a clear resource ('approved sites in the llmsmap.ru catalog'), and it lists the returned fields. It clearly implies a listing operation, but it does not explicitly differentiate from the sibling search_catalog, which prevents a 5.
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 guidance on when to use list_catalog versus search_catalog, and no exclusions or alternatives are mentioned. The agent can only infer from the tool name that list is for broad browsing and search is for targeted queries.
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.