Skip to main content
Glama

Clients our messages do not reach

dosai_list_undelivered
Read-onlyIdempotent

WhatsApp contacts marked "not delivered": our message hung on one tick for three days and the person has not written since (kind undelivered), or the number blocked us (kind blocked). Follow-ups and broadcasts skip them. Up to 200, newest first: conversation id, name, phone, when it was marked.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_list_undelivered"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world, so the description's job is to add behavior, and it does: a hard cap of 200 records, newest-first ordering, and the operational consequence that follow-ups and broadcasts skip these contacts. It does not say what happens beyond the 200 cap or whether results can be paged.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Front-loaded with the definition of the target set, then the operational consequence, then the return shape and cap. Dense but every clause earns its place; the long first sentence is slightly overloaded but readable.

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?

With no output schema, the description compensates by enumerating returned fields (conversation id, name, phone, marked-at) and the ordering and size limits. A one-parameter read tool is adequately covered, though the behavior past the 200-record cap is unspecified.

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?

There is a single required project_id and the schema already documents it at 100% coverage, including its source (dosai_list_projects). The description adds no further meaning about the parameter, which is acceptable but not enriching.

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 names the resource precisely (WhatsApp contacts marked "not delivered") and defines the two qualifying kinds, undelivered and blocked, so an agent knows exactly what set is returned. It stops short of naming a sibling such as dosai_list_contacts or dosai_restore_undelivered, so differentiation is by content rather than explicit routing.

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?

Usage is only implied: the note that follow-ups and broadcasts skip these contacts tells the agent why the list matters for auditing reachability, but there is no explicit when-to-use, when-not-to-use, or pointer to the restore sibling for acting on them.

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