Share by DeltaBreen

get_delivery_status

Read-only

Per-recipient delivery status for a share you emailed to named people: for each address, whether they have opened and downloaded it and when, plus the share's total downloads and, for a share of several files, how many of them each person took (numbers only). Keyless and without IP addresses — enough to say 'Alice downloaded it, Bob has not' and nudge, nothing more. get_receipts gives the who-did-what timeline.

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": {
      "share_id": "<share_id>"
    },
    "name": "get_delivery_status"
  }
}

Input Schema

Name	Required	Description	Default
`share_id`	Yes	The share's id (uuid).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

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 openWorldHint=false, so the safety profile is covered. The description adds meaningful behavioral scope beyond that: it is keyless, excludes IP addresses, and returns 'numbers only — nothing more', which meaningfully bounds what the agent can expect. It does not discuss error or empty-share cases, keeping it below a 5.

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?

Purpose and returned fields are front-loaded, then scope limits, then the sibling pointer — a logical flow with little waste. The parentheticals and em-dash asides make it dense but each clause carries information.

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

Completeness5/5

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

For a read-only, single-parameter tool with full schema coverage and no output schema, the description covers what it returns, its limits, and the sibling alternative. Nothing an agent needs to invoke 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?

With a single parameter and 100% schema coverage, the schema already documents share_id as a uuid. The description adds the useful qualifier that the share must be one emailed to named people, narrowing which share_id values apply — a small but real addition over 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?

The description states a specific verb and resource — per-recipient delivery status for an emailed share — and enumerates exactly what is returned (opened/downloaded per address, timestamps, total downloads, per-file counts). It distinguishes itself from get_receipts by naming that sibling at the end.

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 gives clear usage context ('enough to say Alice downloaded it, Bob has not and nudge') and points to get_receipts for the timeline, effectively routing the agent. It stops short of explicitly saying when NOT to use it, but the alternative is named.

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

All Share by DeltaBreen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?