list_communitiesRetrieve Thunderstore game communities as identifiers and names to select a community for mod searches or pack checks. Supports optional filtering and caches results for 24 hours.
List game communities (identifier + name) on Thunderstore. Cached 24h.
| Name | Required | Description | Default |
|---|---|---|---|
| filter | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network behavior are covered. The description adds one genuinely non-obvious trait: results are cached for 24h, which matters for staleness expectations. It stops there, saying nothing about ordering, size of the result set, or whether the cache is bypassable.
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?
Two tight sentences, front-loaded with the purpose and followed by the caching note; nothing is padded. It is close to optimally sized for a trivial read tool.
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 zero-required-parameter read tool with no output schema, the description covers the resource and return fields, which is most of what an agent needs. The undocumented filter parameter and the absence of guidance on consuming the identifiers leave a real 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?
One parameter (filter) has 0% schema description coverage, so the description carries the full burden and says nothing about it. It's unclear whether filter is a substring/prefix match on name or identifier, case sensitivity, or behavior when empty — the caller must guess.
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?
Specific verb+resource ("List game communities ... on Thunderstore") and even names the returned fields (identifier + name), so an agent knows exactly what comes back. It doesn't explicitly distinguish itself from siblings like search_mods or resolve_dependencies, but the resource noun makes the separation obvious.
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?
No statement of when to call this versus alternatives, and no mention that the identifiers returned are inputs to the other community-scoped tools (search_mods, resolve_dependencies). The use case is inferable but never stated, and no exclusions or prerequisites are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.