List multi-tenant organizations managed in OpenWISP. Filter by organization name or slug to retrieve the groups you need.
[Category: Organizations] List multi-tenant organizations managed within OpenWISP. (HTTP GET /api/v1/users/organization/)
| Name | Required | Description | Default |
|---|---|---|---|
| search | No | Filter by organization name or slug |
Changes observed during successful MCP inspections.
v0.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the HTTP method and endpoint (GET /api/v1/users/organization/), which signals a safe read operation, but says nothing about pagination, result limits, or authentication requirements.
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 compact sentence with the category tag and endpoint appended; the action and resource are front-loaded with no wasted prose.
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 simple one-parameter list tool with no output schema, the core is covered, but pagination behavior and what the list actually returns remain unaddressed. Adequate but not complete.
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?
Schema coverage is 100% with a single self-documented 'search' parameter, so the baseline is 3. The description adds no filtering syntax or matching behavior beyond what the schema already states.
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?
States a specific verb (list) and resource (multi-tenant organizations) plus the category tag and underlying endpoint. An agent can distinguish it from other list tools by resource name, though it never explicitly contrasts with siblings like openwisp_get_organization_geo_settings.
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 guidance on when to use this versus other organization-related tools, nor any mention that the search parameter enables filtering. Usage is only implied by the word 'List'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.