Skip to main content
Glama
Sign In

Goptin

by com.goptin
OverviewDiscussionsAdmin

get_digest

Read-only

Read the user's latest daily digest (one per workspace): a summary of the last 24h across all accounts, tasks due today/overdue, high-priority tickets, and conversations waiting for the user's reply. Start the day here.

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_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true; the description adds meaningful behavior beyond that: it is the 'latest' digest, one per workspace, and covers a rolling 24h window plus due/overdue and awaiting-reply items. It does not say what happens when no digest exists or how stale 'latest' can be.

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?

Two tightly written sentences: the main purpose and contents come first, and the short 'Start the day here' directive earns its place as usage guidance. No filler.

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 and no parameters, the description carries the full burden of explaining the return value, and it does so by enumerating the digest's sections. Minor gap: 'one per workspace' is ambiguous about which workspace's digest is returned when no identifier is supplied, and empty/error behavior is unstated.

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?

There are zero parameters, so the baseline is 4. The description appropriately focuses on what the tool returns rather than on input semantics.

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 (read) and resource (latest daily digest) and enumerates the digest's contents: 24h summary across accounts, tasks due/overdue, high-priority tickets, and conversations awaiting reply. This distinguishes it in substance from sibling list_* tools, though it does not name a sibling explicitly.

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?

'Start the day here' gives a clear usage context (beginning of a session/day) and implies this should be consulted before drilling into individual list tools. No explicit when-not-to-use or named alternatives, which keeps it short of a 5.

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

All Goptin toolsInspect
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