Skip to main content
Glama

list_marketplaces

Retrieve a list of all plugin marketplace repositories, optionally filtering to only enabled ones.

Instructions

List all registered plugin marketplace repositories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabled_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations provided, the description fails to disclose behavioral details such as read-only nature, authorization requirements, or pagination. It merely states the action without additional context.

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?

The description is a single, concise sentence that is front-loaded with the key information. Every word is necessary and no extraneous details are included.

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

Completeness3/5

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

While the tool is simple and has an output schema, the description lacks explanation of the optional parameter, making it incomplete for full understanding. It covers the core action but not the variability.

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?

The parameter 'enabled_only' is not mentioned in the description, and the schema has 0% description coverage. The description adds no meaning beyond the schema, leaving the agent to infer the parameter's purpose.

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

Purpose5/5

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

The description clearly states the tool's action (list) and resource (registered plugin marketplace repositories), distinguishing it from sibling tools like add_marketplace and remove_marketplace.

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?

No explicit guidance on when to use this tool versus alternatives is provided. However, as a simple listing tool, its usage is implied for viewing marketplaces before adding or removing them.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yusufkaraaslan/Skill_Seekers'

If you have feedback or need assistance with the MCP directory API, please join our Discord server