Skip to main content
Glama

Find graded MCP servers

find_alternatives
Read-onlyIdempotent

Find better-graded MCP server alternatives in the same category by passing a server name or package, or browse and filter graded servers by category, search term, or minimum grade.

Instructions

List TrustedMCP-graded MCP servers, best grade first. Filter by category ('databases', 'browser automation'), a search term, or the minimum grade; or pass instead_of with a server name or package to get better-graded servers in its category.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoSearch term matched against name, vendor and summary
categoryNoCategory name or slug
min_gradeNoLowest grade to include (default B)B
instead_ofNoA server to replace: name, slug, package or URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds result ordering ('best grade first') and the default-grade behavior, but says nothing about result volume, pagination, or what a graded entry contains. With annotations carrying the safety burden, this is adequate but thin.

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

Conciseness5/5

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

Two sentences, zero filler, with the core operation and ordering front-loaded before the filter and replacement modes. Every clause maps to a parameter or a behavioral fact.

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

Completeness4/5

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

All five parameters are optional and the description covers four of them; `limit` is left to the schema, which documents it with a default and bounds. With annotations covering safety and no output schema to explain, an agent has what it needs to call this correctly.

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

Parameters4/5

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

Schema coverage is 80%, so the baseline would be 3, but the description earns more: it supplies concrete category examples ('databases', 'browser automation') for a free-form string, and explains that `instead_of` accepts a server name or package and implicitly scopes results to that server's category, a semantic not stated in the schema.

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 names a specific verb and resource ('List TrustedMCP-graded MCP servers') and states the ordering ('best grade first'), so the operation is unmistakable. It does not name or distinguish itself from siblings like lookup_server or registry_lookup, which keeps it short of a 5.

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

Usage Guidelines4/5

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

It spells out the two usage modes: filtering by category, search term, or minimum grade, versus passing `instead_of` to surface better-graded replacements in that server's category. That is clear situational context, though it offers no exclusions or routing guidance relative to the sibling lookup tools.

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