helloasso_get_organizationRetrieve public details of a HelloAsso organization by slug, including name, description, address, logo, and URLs, to display or verify association information.
Public details of a HelloAsso organization (name, description, address, logo, URLs...).
| Name | Required | Description | Default |
|---|---|---|---|
| orgSlug | No | Organization slug (as in helloasso.com/associations/<slug>). Defaults to HELLOASSO_ORG_SLUG. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that only *public* details are exposed, which is meaningful context, but says nothing about auth requirements, error behavior for unknown slugs, or default-slug resolution.
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?
One short sentence, front-loaded with the resource and immediately followed by the returned field categories. No waste, though it is a fragment rather than a full directive sentence.
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, the description usefully enumerates what fields come back, and the single parameter is fully documented in the schema. What remains missing (auth, error cases) is minor for a simple public read.
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 single orgSlug parameter has 100% schema coverage, including the helloasso.com/associations/<slug> format and the HELLOASSO_ORG_SLUG default. The description adds nothing about the parameter, so baseline 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?
Names the resource (HelloAsso organization) and the returned content (name, description, address, logo, URLs), with 'get' implied by the title. It is reasonably distinguishable from helloasso_list_my_organizations because it fetches one org's details, though the description never explicitly contrasts the two.
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?
Usage is only implied: an agent infers you call this to fetch a single org's profile. There is no statement of when to prefer it over helloasso_list_my_organizations, nor any prerequisite such as needing a slug.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.