fetchFetch the full public details of one Mozilla Data Collective dataset by id or slug: description, organization, task, locale, license, format, size, pricing, and its page URL.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Dataset id or slug, as returned in the id field of search results. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior; the description adds that the data is 'public' and enumerates which fields will be returned. This extends the annotation context without contradicting it.
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 entire description is one dense sentence: the operation, input key, and expected return fields are all front-loaded with no filler or repetition of the title.
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?
For a one-parameter read operation with full annotations, the description covers what is fetched and what is returned well enough. It omits explicit not-found or error behavior, but the absence of an output schema and low complexity keep this a minor gap.
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?
Schema coverage is 100% and the parameter description already states it is a dataset id or slug from search results. The tool description adds no new semantic detail for the parameter beyond what the schema provides.
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?
Description names a specific verb ('Fetch'), a bounded resource ('one Mozilla Data Collective dataset'), and the lookup key ('by id or slug'), then enumerates the returned details. This is distinguishable from siblings 'search' and 'list_filters' without needing their schemas.
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 description makes clear this is for retrieving full details for a single known dataset, which implies a post-search or post-list step. It does not explicitly name when to prefer 'search' or 'list_filters', so it falls short of full exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: list_filters enumerates accepted filter values, search returns matching dataset summaries, and fetch retrieves full details for a single dataset. There is no meaningful overlap or ambiguity between them.
All names are lowercase imperative verbs and are easy to understand. list_filters follows a verb_noun pattern while search and fetch are single-word verbs, but the inconsistency is minor and does not hurt usability.
Three tools is an appropriate, well-scoped size for a read-only catalog search and retrieval server. Each tool serves a necessary part of the discovery workflow: filter discovery, search, and detail fetch.
The tool surface fully covers the stated domain: discover available filters, search the catalog, and fetch detailed dataset information. There are no obvious dead ends or critical missing operations for this read-only purpose.