Skip to main content
Glama
Sign In
Missive MCP

Missive MCP

by kanjidoc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

missive_get_contact

Read-only

Retrieve a single contact from your Missive team inbox by providing its UUID. Get the contact's details or receive a 404 error if the contact has been deleted.

Instructions

Fetch a single contact by its UUID. A deleted contact returns 404. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contact_id": "<contact_id>"
    },
    "name": "missive_get_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idYesUUID of the contact to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The description clearly states it is read-only, matching the readOnlyHint annotation, and adds that a deleted contact returns 404, providing useful behavioral context beyond annotations.

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 short sentences, front-loaded with the action, and every word adds value without redundancy.

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

Completeness4/5

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

The description conveys the essential behavior and read-only nature, but lacks explicit mention of the return format (e.g., the contact object), which could be helpful given no output schema.

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?

The only parameter, contact_id, is described in the schema as 'UUID of the contact to fetch,' and the description adds 'by its UUID' which overlaps. With 100% schema coverage, baseline 3 is appropriate.

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 explicitly states 'Fetch a single contact by its UUID,' using a specific verb and resource, and distinguishes from sibling tools like missive_list_contacts which fetches multiple contacts.

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

Usage Guidelines3/5

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

The description implies usage when a UUID is available but does not explicitly contrast with alternatives like missive_list_contacts or provide guidance on when not to use it.

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