missive_list_contact_groupsList contact groups or organizations within a contact book. Missive: GET /contact_groups.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | Which kind to list: "group" or "organization". | |
| limit | No | Max records to return. | |
| offset | No | Number of records to skip (offset pagination). | |
| contact_book | Yes | The contact book id (required). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations (readOnlyHint: true) already indicate it's a safe read operation. The description adds no further behavioral details (e.g., pagination, error handling) beyond the basic 'list' action. It meets the minimal bar but does not enrich the annotation.
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 extremely concise with two sentences: one stating purpose and one giving the API endpoint. No wasted words; front-loaded with essential 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?
Given the simplicity of the tool (list operation, no output schema), the description covers the basic purpose but lacks details on pagination behavior, ordering, or return format. It is adequate but not comprehensive.
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 input schema already has 100% description coverage for all parameters, so the baseline is 3. The description does not add any additional parameter semantics beyond what the schema provides.
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 clearly states the action ('list') and the resource ('contact groups or organizations within a contact book'), distinguishing it from sibling tools like missive_list_contacts or missive_list_organizations. The API endpoint is also provided.
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 explicit when-to-use or when-not-to-use guidance is given, but the required parameters (contact_book, kind) imply the context. The agent must infer usage from similar tools; no alternatives are mentioned.
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.
Every tool targets a unique resource-action combination (e.g., missive_get_contact vs missive_list_contacts). There is no overlap in functionality; the purposes are clearly distinct.
All tool names follow a strict 'missive_verb_noun' pattern in lowercase snake_case. Verbs are limited to create, get, list, and update, applied consistently across resources.
With 19 tools, the server is slightly above the ideal range (3-15) but still reasonable for covering multiple resources like contacts, conversations, messages, and lists. Each tool serves a specific purpose without unnecessary redundancy.
Core workflows are covered: listing, getting, creating contacts/drafts, managing conversations, and viewing sub-items. Minor gaps exist (no update for contacts, no delete for any resource), but these are acceptable for an initial release.