Skip to main content
Glama

Which Marketplaces Are Loaded

marketplace_sources
Read-onlyIdempotent

List which marketplace connectors are actually mounted and which were skipped, so you can distinguish a missing source from a source that simply returned no results.

Instructions

List which connectors this unified server actually mounted.

Why this exists

Connectors are imported defensively, so a missing dependency removes a marketplace instead of killing the server. That is the right failure mode, but it is invisible from the client: absent tools look the same as a source that simply found nothing. Call this before concluding a marketplace has no results — if it is in skipped, it was never queried at all.

Full field list and error codes: guide://marketplace/marketplace_sources.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
mountedNo
skippedNo
needs_cdpNo
capabilitiesNo
mounted_countNo
skipped_countNo
server_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.8.0
    • addedOutput schema / properties / needs_cdp
      Added value: +{}
  2. Changed1 schema field changedv2.1.0
    • addedOutput schema / properties / capabilities
      Added value: +{}
  3. First observedv1.5.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the important non-obvious behavior: connectors are imported defensively, a missing dependency silently removes a marketplace, and absence of tools looks identical to a source that found nothing. It also points to a guide resource for the full field list and error codes.

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 core instruction is front-loaded in the first line, and the 'Why this exists' section justifies itself by explaining a silent failure mode. It is slightly longer than strictly necessary for a no-argument listing tool, but no sentence is filler.

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

Completeness5/5

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

An output schema exists, so the description need not enumerate return fields, yet it still explains the one field whose meaning matters (`skipped`) and links a guide for the rest. For a zero-parameter introspection tool this is complete: an agent knows what it returns, why it matters, and when to call it.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It does not need to explain inputs and correctly spends its words on output semantics instead.

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?

States a specific verb and resource: list which connectors the unified server actually mounted, including a `skipped` category. This is unmistakably a diagnostics/introspection tool and is clearly separable from search or card siblings, which query marketplaces rather than report which ones loaded.

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?

Gives an explicit triggering condition: call this before concluding a marketplace has no results, because a `skipped` entry means it was never queried. That is real when-to-use guidance. It stops short of naming an alternative such as marketplace_health or compare_sources for the case where sources are loaded and you want to compare them.

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