Your Echo — The A2A-native PR & Outreach Agent

discover_communities

Find targeted communities and events for your niche, filtered by type like conferences, webinars, or Slack groups. Input your audience's interests and location to discover relevant gatherings.

Instructions

Find where your audience gathers — filtered by category (conference, webinar, meetup, networking_event, linkedin_group, facebook_group, slack_community, discord_server, subreddit, professional_association, podcast, newsletter). Public demo, no API key needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "niche": "<niche>",
      "category": "<category>"
    },
    "name": "discover_communities"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`niche`	Yes
`category`	Yes
`location`	No	Optional city/region or 'remote'.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.2Jul 9, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only states 'Public demo, no API key needed', implying it's a read-only demo endpoint, but does not disclose any behavioral traits such as data nature, rate limits, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (two short sentences) but at the cost of missing important details. It is front-loaded with the main purpose, but could benefit from additional context without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, no output schema, no annotations, and multiple sibling tools, the description lacks critical information about return format, pagination, and data interpretation, making it incomplete for proper tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 25% (only location has description). The description lists category values but adds no meaning for niche or limit beyond the schema's enum and integer constraints. It does not compensate for the low coverage.

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 uses a clear metaphor 'Find where your audience gathers' and lists 12 specific community categories, making the tool's purpose immediately understandable. However, it does not differentiate from similar sibling tools like discover_events or find_linkedin_groups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like discover_events or find_linkedin_groups. The phrase 'Public demo, no API key needed' gives a hint but does not provide decision criteria for tool selection.

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

Deploy Server