Skip to main content
Glama

daily_brief

Read-onlyIdempotent

Get a one-call standup summary of overdue, due-today, and no-deadline task counts, urgent tasks, unread chats, and per-project open and overdue totals to see what needs attention.

Instructions

One-call standup: my overdue / due-today / no-deadline task counts with the urgent tasks listed, unread chats, and per-project open and overdue counts. Good first call for "what's going on?".

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the description only needs to add context, and it does: it discloses the aggregate's composition (counts plus the urgent task list plus chats) so the agent knows it is a synthesized view rather than a raw list. It does not mention cost, limits, or how large the urgent-task list may grow, which is a minor residual gap for an open-world read.

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?

The name-defining frame ('One-call standup') is front-loaded, followed by a tight enumeration of the returned sections and a single closing usage cue. Three sentences, no filler, and each clause carries distinct information an agent needs.

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 an output schema present, return-value shape does not need explaining, and the zero-parameter schema needs no documentation, so the description's main burden is scope, which it handles well. The only missing piece is how this aggregate relates to the overlapping sibling summary/count tools when the agent must choose between them.

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?

The tool takes no parameters, so the baseline is 4. The description implicitly confirms callers need no arguments, which is consistent with the empty schema, but there is no parameter meaning to add.

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?

The description uses a concrete framing ('One-call standup') and enumerates exactly what the payload contains: overdue/due-today/no-deadline task counts, urgent tasks listed, unread chats, and per-project open/overdue counts. That is specific verb+resource clarity rather than a restatement of the name. It stops short of differentiating itself from close siblings such as get_dashboard_summary or get_task_counts, which an agent may also reasonably consider.

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 a clear entry-point cue: 'Good first call for "what's going on?"', which tells the agent when this tool is the right opening move. It does not name when-not to use it or which alternative to prefer for narrower needs (e.g., per-project counts when the aggregate is too broad), so it falls 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.