get_impact_enginesDiscover NCTR Impact Engine communities. Impact Engines are passion-based communities within NCTR — each focused on a different lifestyle vertical. Members can join any Impact Engine to connect with like-minded people and access community-specific experiences.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Filter by category (Powersports, Lacrosse, Entertainment, Skilled Trades, Recovery, Wellness) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes what Impact Engines are, but not what the tool actually returns, whether it supports filtering, or whether it has side effects like joining a community.
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 three sentences and front-loads the purpose. The additional context about Impact Engine communities is useful, though slightly verbose for a simple list 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?
With no output schema and no annotations, the description is minimally sufficient: the name and first sentence imply a list operation, and the schema covers the optional filter. However, return format and filtering behavior are left implicit.
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?
The schema description for the category parameter is 100% complete, listing all possible values. The tool description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 applies.
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 opens with 'Discover NCTR Impact Engine communities', using a specific verb and resource. It clearly distinguishes the tool from siblings focused on promotions, requirements, funding, and search.
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 first sentence 'Discover NCTR Impact Engine communities' gives clear context for when to use the tool. It does not mention explicit exclusions or alternatives, but the purpose is unambiguous among the sibling tools.
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.