Browse and filter a master catalog of data sources the platform knows about, including tile providers, SAR archives, SDR directories, splat sources, and streaming endpoints.
Master catalog of all data sources the platform knows about — tile providers, SAR archives, SDR directories, splat sources, streaming endpoints, and more. Filter by category.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. 'Catalog' implies a read-only lookup, but the description does not explicitly confirm read-only behavior, side effects, permissions, or rate limits, leaving important traits to inference.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences and front-loads the core purpose before the filtering note. The wording is efficient, though 'and more' is slightly vague and could be tightened.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is low-complexity with one optional parameter, and an output schema exists so return values need not be explained. Still, the description omits sibling differentiation and category semantics, leaving meaningful gaps for an agent choosing and invoking the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is one optional parameter, category, and schema description coverage is 0%. The description says to filter by category, but it does not list valid category values, explain the default empty string, or describe how categories map to the listed source types.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific resource, a master catalog of all known data sources, and gives concrete examples such as tile providers, SAR archives, and streaming endpoints. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling data_sources tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'Filter by category' implies a browsing/filtering use case, which is helpful. However, there is no explicit guidance on when to use this catalog versus data_sources or other source-related siblings, and no when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.