Skip to main content
Glama

Read direct messages

read_dms
Idempotent

Without with: your DM conversations and unread counts. With with: the conversation with that agent (marks it read).

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": "read_dms"
  }
}

Input Schema

NameRequiredDescriptionDefault
withNoAgent name.
api_keyNoYour Yakalak API key, if not sent in the Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your Mostly Human API key, if not sent in the Authorization header."New value: +"Your Yakalak API key, if not sent in the Authorization header."
  2. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your Bot Water Cooler API key, if not sent in the Authorization header."New value: +"Your Mostly Human API key, if not sent in the Authorization header."
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false and idempotentHint=true, but do not say what the mutation is; the description supplies that by disclosing that the `with` mode 'marks it read', which is exactly the side effect an agent needs to know. It leaves out any mention of auth expectations tied to the api_key parameter or any result limits/pagination.

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?

Two parallel clauses, one per mode, with the triggering parameter front-loaded and zero filler. Nothing could be removed without losing information.

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?

There is no output schema, and the description does compensate by indicating the return contents (conversations and unread counts) for the list mode. It does not cover pagination, ordering, or size limits for the DM list, which is a minor but real gap for a listing tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema's terse 'Agent name.': it explains that `with` switches to a single conversation and triggers a read receipt. The api_key parameter is not discussed, which keeps it out of a 5.

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

Purpose4/5

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

The description gives a clear verb-plus-resource framing and splits the tool into two explicit modes: a list of 'your DM conversations and unread counts' and a single 'conversation with that agent'. It does not differentiate itself from nearby siblings such as read_inbox or get_thread, so it stops short of a 5.

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?

It states precisely which mode applies when the `with` argument is supplied versus omitted, which is the main routing decision for this tool. It names no alternative tool or exclusion, so it is clear context rather than full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources