get_communityGet one local community's public details: what it runs, where, in which languages, the people and venues involved, and events it organizes. Use with a slug from search_communities. Group chat invite links and contacts are only on the community's page, not returned here.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Community slug from search_communities. |
Changes observed during successful MCP inspections.
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 real value beyond that by disclosing the content scope of the response and, importantly, what is deliberately omitted (group chat invite links and contacts), which prevents an agent from assuming a complete record.
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 sentences, no filler, with the capability statement front-loaded and the usage caveat second. Every clause carries either content scope or routing information.
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?
No output schema exists, so the description must convey return content — it does, listing the facets returned and explicitly noting what is absent. Combined with annotations covering safety and one fully documented parameter, nothing needed to invoke this correctly is missing.
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?
Single parameter with 100% schema description coverage, so the schema already defines the slug and its origin. The description restates the slug provenance ('from search_communities') without adding format, validation, or resolution behavior beyond the schema, matching the baseline of 3.
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 with an explicit enumeration of the returned facets ('what it runs, where, in which languages, the people and venues involved, and events it organizes'). This clearly separates it from siblings like get_event or get_venue, which return a single entity type.
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?
Explicitly states the required input provenance ('Use with a slug from search_communities'), routing the agent through the sibling search tool first. It also flags an exclusion — invite links and contacts are only on the community's page — which is useful scope guidance, though it stops short of naming a dedicated alternative tool for those.
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.