OrgLines

Get digest

get_digest

Read-only

Preview the caller's composed proactive digest (TZ-IDEAS-30). 'period' selects the template: 'daily' = the morning brief (tasks due today/overdue, today's events, active goals, pending inbox, upcoming subscription charges + warranty expiries); 'weekly' = the Sunday review (tasks completed this week, goal progress, weekly spend, the week ahead); 'ai_summary' = 'what your AI did this week' (a metadata-only aggregation of your own mcp_tool_call events — counts by tool/module + confirmed writes). Read-only, composed deterministically from ONLY your own data in your active workspace (no server-side LLM). Returns the ready-to-send message plus a structured 'context' the AI can elaborate on. Delivery is separate (the per-workspace digest opt-ins).

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": {
      "period": "<period>"
    },
    "name": "get_digest"
  }
}

Input Schema

Name	Required	Description	Default
`period`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, yet the description adds substantial non-structured context: composition is deterministic, uses ONLY the caller's own data in the active workspace, and involves no server-side LLM. It also states the return shape (ready-to-send message plus a structured 'context' for elaboration) and separates delivery from generation.

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 the period selector are front-loaded, and almost every clause carries operational information. Minor noise: the internal ticket reference '(TZ-IDEAS-30)' and a very dense single-paragraph layout with heavy parenthetical nesting, which slightly hinders scanning.

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 single-enum read tool with no output schema, the description covers everything an agent needs: what each period yields, the data-scope guarantee (own data, own workspace, no LLM), the return shape, and where delivery happens instead. Nothing material is left to inference.

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

Parameters5/5

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

Schema description coverage is 0% and the single parameter is enum-only, so the description must carry the meaning — and it does, defining each enum value by the concrete data it includes (tasks due/overdue, today's events, subscription charges, weekly spend, mcp_tool_call metadata aggregation, etc.). An agent can choose a value from the description alone.

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?

States a specific verb and resource ('Preview the caller's composed proactive digest') and then defines the branch dimension: 'period' selects the template, with each of daily/weekly/ai_summary spelled out in terms of contents. No sibling tool in the list is a digest generator, so an agent can identify this unambiguously.

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?

The description makes the selection rule explicit ('period' selects the template) and gives enough content detail per period that an agent can pick one. It also draws the use/not-use boundary against delivery ('Delivery is separate (the per-workspace digest opt-ins)'), clarifying this is a preview only. It does not name another tool as an alternative, but none of the siblings appears to overlap.

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

All OrgLines 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?