ragmap

Top recommended servers

rag_top_servers

Returns recommended retriever MCP servers with smart defaults, allowing filtering by categories, score, reachability, and type to find the best retrieval server for your needs.

Instructions

Get top recommended retriever MCP servers with smart defaults.

Tool call template

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": "rag_top_servers"
  }
}

Input Schema

Name	Required	Description	Default
`categories`	No
`minScore`	No
`hasRemote`	No
`reachable`	No
`reachableMaxAgeHours`	No
`localOnly`	No
`serverKind`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0May 25, 2026

TDQS

C2.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description must disclose behavior. It only states 'get top recommended' but does not confirm read-only, mention side effects, permissions, rate limits, or return format. 'Smart defaults' is vague and unhelpful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, short sentence (8 words), which is efficient but lacks front-loaded key details. It communicates the basic purpose but omits critical information, making it borderline under-specified rather than concisely informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 optional parameters, no output schema, and no annotations, the agent needs extensive context. The description provides none about output format, parameter roles, or expected behavior. It fails to equip an agent for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description provides no parameter explanations. The 8 parameters (categories, minScore, etc.) are completely undocumented in the description. 'Smart defaults' does not clarify parameter purpose or interaction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description includes a clear verb ('Get') and resource ('top recommended retriever MCP servers'), indicating a retrieval operation. However, it does not differentiate from sibling tools like rag_find_servers, which also retrieves servers. The mention of 'smart defaults' hints at automated filtering but lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as rag_find_servers. There are no exclusions, prerequisites, or context for optimal usage. The description is insufficient for choosing between tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server