Skip to main content
Glama
Sign In
Missive MCP

Missive MCP

by kanjidoc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

missive_list_organizations

Read-only

Lists organizations you belong to and returns their IDs and names, enabling you to find the organization ID needed as a filter for other tools.

Instructions

Lists the organizations the API token owner is part of (id, name). Use this to find the organization id used as a filter or default by other tools. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "missive_list_organizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of organizations to return. Default 50, max 200.
offsetNoOffset used to paginate results. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The description declares the tool as 'Read-only', which aligns with the annotation readOnlyHint=true. It adds context that it returns id and name, but no additional behavioral traits are needed given 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.

Conciseness5/5

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

The description is two sentences, front-loaded with the core purpose, and contains no unnecessary words.

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

Completeness5/5

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

For a simple list tool with no output schema, the description explains what is returned (id, name) and how to use the result (to get organization IDs). It is complete for the tool's complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents limit and offset. The description does not add any further meaning to the parameters, meeting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'lists' and resource 'organizations', and specifies the return fields (id, name). It distinguishes itself from sibling list tools by focusing on organizations.

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

Usage Guidelines4/5

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

The description explicitly tells the agent to use this tool to find organization IDs for filtering in other tools. It provides clear context for when to use it, though it does not state when not to use alternatives.

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

Deploy Server

Other Tools