Skip to main content
Glama

List Available Marketplaces

compare_sources
Read-onlyIdempotent

Reports which marketplaces this installation can query, helping diagnose partial comparisons by distinguishing missing connectors from marketplace refusals.

Instructions

Report which marketplaces this installation can actually query.

Call this first when a comparison comes back partial: it distinguishes "the connector isn't installed" from "the marketplace refused us", which need completely different fixes.

Full field list and error codes: guide://compare/compare_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": "compare_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuine behavioral value by framing the tool as a diagnostic that disambiguates two failure classes and pointing to a guide for error codes. It doesn't say what the report looks like beyond the output schema, which is acceptable here.

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?

Three short sentences, front-loaded with the core purpose, followed by the triggering condition and a pointer to deeper documentation. Nothing is repeated and no sentence is redundant.

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?

An output schema exists, so return values need not be described, and the error-code guide reference covers deeper detail. What's missing is the relationship to the near-identical sibling tools marketplace_sources and marketplace_health, which an agent would need in order to choose 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?

The tool takes zero parameters, so there are no parameter semantics to document and the baseline of 4 applies. The description correctly avoids inventing arguments and notes the guide reference instead.

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 gives a concrete verb and resource: report which marketplaces this installation can actually query. That resolves the ambiguity of the opaque name 'compare_sources' and the broad title. It does not name the very similar sibling tools (marketplace_sources, marketplace_health), so it stops short of full differentiation.

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 states a clear trigger: call this first when a comparison comes back partial, and explains why (distinguishing a missing connector from a marketplace refusal). That is actionable context. However, it never mentions what to use otherwise or how it differs from marketplace_sources and marketplace_health, which appear to overlap heavily with this tool.

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