meta-agent-tools

list_listings

Public mosaic of live MCP servers, skills and plugins.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Free text over the name, the tagline and the description. Kind, topic and transport words become filters.
`low`	No	`1` includes `low` listings in the result. Only valid together with `q`.
`kind`	No	Which kind of resource to fetch.
`sort`	No	Result order. Without it, a query is ranked by relevance and a plain listing by arrival.	relevancia when q is set, recent otherwise
`category`	No	Category declared by whoever published.
`interpret`	No	`0` disables query understanding and searches the raw string.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedSep 7, 2026

changedInput schema / properties / sort / default

Previous value: -"recent"New value: +"relevancia when q is set, recent otherwise"

changedInput schema / properties / sort / description

Previous value: -"Result order."New value: +"Result order. Without it, a query is ranked by relevance and a plain listing by arrival."

changedInput schema / properties / sort / enum

Previous value: -[
-  "recent",
-  "likes",
-  "visits"
-]New value: +[
+  "relevancia",
+  "recent",
+  "stars",
+  "likes",
+  "visits",
+  "nome"
+]

Changed2 schema fields changedSep 7, 2026

addedInput schema / properties / interpret

Added value: +{
+  "description": "`0` disables query understanding and searches the raw string.",
+  "enum": [
+    "0"
+  ],
+  "type": "string"
+}

changedInput schema / properties / q / description

Previous value: -"Free text over the name, the tagline and the description."New value: +"Free text over the name, the tagline and the description. Kind, topic and transport words become filters."

Changed9 schema fields changedSep 6, 2026

addedInput schema / properties / category / description

Added value: +"Category declared by whoever published."

addedInput schema / properties / kind / description

Added value: +"Which kind of resource to fetch."

addedInput schema / properties / kind / enum

Added value: +[
+  "mcp",
+  "skill",
+  "plugin"
+]

addedInput schema / properties / low / description

Added value: +"`1` includes `low` listings in the result. Only valid together with `q`."

addedInput schema / properties / low / enum
```
Added value: +[
+  "1"
+]
```

addedInput schema / properties / q / description

Added value: +"Free text over the name, the tagline and the description."

addedInput schema / properties / sort / default
```
Added value: +"recent"
```
addedInput schema / properties / sort / description
```
Added value: +"Result order."
```

addedInput schema / properties / sort / enum

Added value: +[
+  "recent",
+  "likes",
+  "visits"
+]

First observedSep 5, 2026

TDQS

C2/5.0

Behavior1/5

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

The description is silent on behavior. It does not indicate whether the operation is read-only, whether it has side effects, or what the output looks like. With no annotations, this lack of detail leaves the agent guessing about the tool's effects.

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

Conciseness4/5

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

The description is a single concise sentence with no unnecessary words. It is front-loaded with the subject, though the phrasing is vague. It does not waste space, which is good, but it lacks substance.

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

Completeness2/5

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

The description omits key context such as return format, pagination, or any preconditions. With no output schema and no annotations, the description does not provide enough information for an agent to fully understand the tool's behavior or expectations.

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?

The schema covers all parameters with descriptions, providing some semantic content. However, some descriptions are cryptic (e.g., 'low' and 'interpret') and the short description adds little beyond the schema. Given 100% schema coverage, a baseline of 3 is appropriate.

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

Purpose2/5

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

The description 'Public mosaic of live MCP servers, skills and plugins' is metaphorical and does not clearly state the action. It does not mention 'list', 'search', or 'fetch', leaving the primary purpose ambiguous. The tool name suggests listing, but the description alone is insufficient.

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

Usage Guidelines1/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 sibling tools like list_mcp_servers or get_listing. There is no mention of criteria for choosing this tool over alternatives, leaving the agent without direction.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.5/5.0

Disambiguation4/5

Most tools are clearly separated by resource/action (listings, comments, servers, billing, health). The main ambiguity is among get_listing, get_listing_readme, and go_listing, which all involve retrieving or routing to a listing but return different things.

Naming Consistency4/5

The set mostly follows a verb_noun snake_case convention (create_listing, get_listing_readme, list_comments, like_listing). A few bare endpoint-style names (billing, contact, health, api_index) break the pattern but are still recognizable.

Tool Count4/5

Thirteen tools is a reasonable size and each area—registry, comments, billing, health—has at least one tool. The count is not bloated, though the mixed domains make it feel slightly less focused than a single-purposed server.

Completeness3/5

The listing registry covers create, get, list, like, visit, and readme retrieval, but lacks obvious update/delete operations and any way to create comments. The billing/contact side is also thin, exposing prices and one paid action rather than a fuller payment flow.

Resources

Need Help?