meta-agent-tools

List MCP servers

list_mcp_servers

Read-onlyIdempotent

MCP subregistry (GET /v0.1/servers). Only live kind=mcp. Only kind=mcp and only live. It is the route a generic MCP client knows how to read without knowing this product. GET /v0/servers is an alias of the same resource, kept for whoever already pointed there — this is the canonical URL.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Servers per page.
`cursor`	No	Opaque cursor of the next page, from `metadata.next_cursor`.
`search`	No	Free text over the server's name and description.
`retry_key`	No	Optional retry key, up to 80 ASCII characters; same read for five minutes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

removedInput schema / properties / api_pass

Removed value: -{
-  "description": "MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.",
-  "type": "string"
-}

Changed2 schema fields changedSep 17, 2026

addedInput schema / properties / api_pass

Added value: +{
+  "description": "MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.",
+  "type": "string"
+}

addedInput schema / properties / retry_key

Added value: +{
+  "description": "Optional retry key, up to 80 ASCII characters; same read for five minutes.",
+  "type": "string"
+}

Changed4 schema fields changedSep 6, 2026
- addedInput schema / properties / cursor / description
```
Added value: +"Opaque cursor of the next page, from `metadata.next_cursor`."
```
- addedInput schema / properties / limit / default
```
Added value: +30
```
- addedInput schema / properties / limit / description
```
Added value: +"Servers per page."
```
- addedInput schema / properties / search / description
```
Added value: +"Free text over the server's name and description."
```
First observedSep 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly and idempotent and non-destructive, so safety is covered. The description adds genuine behavioral context the annotations lack: results are filtered to kind=mcp and live, and the same resource is reachable via an alias route. It does not, however, describe pagination or result shape.

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 core facts earn their place, but 'Only live kind=mcp. Only `kind=mcp` and only `live`.' restates the same constraint twice in consecutive sentences, which is wasted space in an otherwise short description.

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?

For a read-only, 0-required-parameter list tool with annotations and a fully documented schema, the description covers scope, filtering, and route aliasing adequately. The only minor gap is leaving 'live' and 'kind=mcp' undefined, which is not essential to call the tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so limit, cursor, search, and retry_key are already documented in the schema. The description adds nothing about parameter syntax or interaction, so the baseline 3 applies.

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?

It states this is the MCP subregistry served from GET /v0.1/servers and that results are restricted to kind=mcp and live, which is enough to tell it apart from siblings like mcp_index_search or list_listings. The phrasing is route-centric rather than verb-centric, but the resource and scope are clear.

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

Usage Guidelines3/5

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

It explains that this is the route a generic MCP client reads and that /v0/servers is kept as an alias, which implies when to prefer it. However, it never states when to use this over the sibling search/index tools (mcp_index_search, list_listings), so selection guidance is only implied.

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

All meta-agent-tools tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?