Skip to main content
Glama

Dayze — Life Context

Get Pending Replies

get_pending_replies
Read-only

Pending Replies (Inbox): the replies the user owes ('who do I owe a reply?'), newest first, or one by reply_id. status: unsent (default; pending + snoozed), sent, dismissed, all. Filter by person_name or person_id. Each reply has reply_id, person_name, person_id (null when unlinked), draft, summary, channel, category, source ids, status, state (unsent | sent | dismissed) and due (owed now; false while snoozed until snooze_until). Read-only. ($0.05; API key required)

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

Input Schema

NameRequiredDescriptionDefault
limitNo1-200, default 50.
statusNoReply state filter: unsent, sent, dismissed or all, e.g. unsent.
reply_idNoRead one reply (ignores the filters).
person_idNoContact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
person_nameNoContact name when there is no person_id, e.g. Alex Chen.

Output Schema

NameRequiredDescriptionDefault
countYes
statusYesThe filter applied: unsent, sent, dismissed or all.
app_urlNo
has_moreYes
pending_repliesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / person_id / description
      Added value: +"Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809."
    • addedInput schema / properties / person_name / description
      Added value: +"Contact name when there is no person_id, e.g. Alex Chen."
    • addedInput schema / properties / status / description
      Added value: +"Reply state filter: unsent, sent, dismissed or all, e.g. unsent."
  2. Changed1 schema field changed
    • changedOutput schema / properties / pending_replies / items / properties / source / properties / kind / description
      Previous value: -"gmail, email or other; or imessage, whatsapp, instagram, signal, telegram when Dayze Desktop detected it (thread_id is then an opaque id)"New value: +"gmail, email or other; imessage, whatsapp, instagram, signal, telegram when Dayze Desktop detected it; or linkedin from a LinkedIn data-export import (thread_id is then an opaque id)"
  3. Changed1 schema field changed
    • changedOutput schema / properties / pending_replies / items / properties / source / properties / kind / description
      Previous value: -"gmail, email or other"New value: +"gmail, email or other; or imessage, whatsapp, instagram, signal, telegram when Dayze Desktop detected it (thread_id is then an opaque id)"
  4. Changed3 schema fields changed
    • addedOutput schema / properties / pending_replies / items / properties / is_private
      Added value: +{
      +  "description": "Always true.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / pending_replies / items / properties / visibility
      Added value: +{
      +  "description": "Always private: Pending Replies have no sharing setting.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / pending_replies / items / required
      Previous value: -[
      -  "reply_id",
      -  "person_name",
      -  "person_id",
      -  "channel",
      -  "category",
      -  "summary",
      -  "draft",
      -  "status",
      -  "state",
      -  "due",
      -  "received_at",
      -  "source"
      -]New value: +[
      +  "reply_id",
      +  "person_name",
      +  "person_id",
      +  "channel",
      +  "category",
      +  "summary",
      +  "draft",
      +  "status",
      +  "state",
      +  "due",
      +  "received_at",
      +  "source",
      +  "visibility",
      +  "is_private"
      +]
  5. Changed1 schema field changed
    • addedOutput schema / properties / pending_replies / items / properties / approved_at
      Added value: +{
      +  "description": "PHI-427: when the owner approved the draft and opened it in Gmail, or null. Dayze never sends; the Gmail sync closes the reply when the email goes out.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  6. Changed2 schema fields changed
    • addedOutput schema / properties / pending_replies / items / properties / due
      Added value: +{
      +  "description": "Owed now: pending, or snoozed with snooze_until passed. False while a snooze runs, and when sent or dismissed.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / pending_replies / items / required
      Previous value: -[
      -  "reply_id",
      -  "person_name",
      -  "person_id",
      -  "channel",
      -  "category",
      -  "summary",
      -  "draft",
      -  "status",
      -  "state",
      -  "received_at",
      -  "source"
      -]New value: +[
      +  "reply_id",
      +  "person_name",
      +  "person_id",
      +  "channel",
      +  "category",
      +  "summary",
      +  "draft",
      +  "status",
      +  "state",
      +  "due",
      +  "received_at",
      +  "source"
      +]
  7. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower; the description still adds order (newest first), the snooze nuance ('due' is owed now, false while snoozed until snooze_until), and an auth/cost disclosure ($0.05; API key required). It does not discuss pagination beyond the limit default, which is already in the schema.

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?

A single dense paragraph that front-loads purpose and question, then defaults, then filters, then return shape. Parentheticals carry the caveats efficiently with no filler sentences.

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?

Safety and auth are covered by annotations plus the cost note, and an output schema exists, so the enumerated field list (reply_id, person_name, draft, summary, etc.) is a mild duplication of structured data rather than necessary content. Nothing an agent needs in order to call it correctly is missing.

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 a baseline of 3 applies, but the description adds real meaning: what 'unsent' expands to, that reply_id overrides all filters, and that person_name is the fallback when there is no person_id. Only the limit and reply_id type details are left to the schema.

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?

Names the resource ('Pending Replies (Inbox)'), gives the user-facing question it answers ('who do I owe a reply?'), and states both access modes (list newest-first, or a single reply by reply_id). The get_/create_/resolve_/update_ sibling split is unambiguous from this phrasing.

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?

Default behavior is spelled out (status defaults to 'unsent', which covers pending + snoozed) and it notes that reply_id ignores the filters, so an agent knows the two call shapes. It does not explicitly route to siblings like resolve_pending_reply, but for a read tool the context is clear enough.

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.