Skip to main content
Glama

list_daily_digest_sends

Read-onlyIdempotent

List recent daily digest send attempts for the approved business. Filter by Today or Tomorrow and inclusive business-local dates (YYYY-MM-DD). claimed_at is Unix milliseconds.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
kindNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description still adds real behavior: dates are interpreted business-local, today/tomorrow are relative windows, and 'approved business' implies an implicit tenant scope with no business_id parameter. It does not mention ordering or whether the limit truncates results.

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?

Two dense sentences with the resource scope front-loaded and no filler. The trailing 'claimed_at is Unix milliseconds' is abrupt and unexplained, keeping it from a 5.

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?

For a four-parameter, all-optional list tool with no output schema and annotations covering the safety profile, the definition supplies the essentials: scope, date semantics, and the time unit of a key returned field. It is thin on result ordering and on how limit interacts with truncation, but nothing critical is missing for a correct call.

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 0%, so the description must carry the load; it clarifies that from/to are inclusive business-local YYYY-MM-DD dates and that kind selects a 'today'/'tomorrow' window. The limit parameter (default 30, max 100) is never explained, and claimed_at is referenced but is not an input parameter, so coverage is partial.

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?

States a specific verb and resource: 'List recent daily digest send attempts for the approved business.' An agent can tell this apart from get_daily_digest_settings and save_daily_digest_settings, but the description never names those siblings or explicitly contrasts read-vs-write on the digest resource.

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

Usage Guidelines2/5

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

The only guidance is a restatement of filter capabilities ('Filter by Today or Tomorrow and inclusive business-local dates'). There is no when-to-use, no when-not-to-use, and no routing to alternatives such as checking digest settings first.

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