Skip to main content
Glama

Get the morning brief

well_get_morning_brief
Read-only

The caller's morning brief of today, as the card the brief sent: its title, at most 3 points (each with its title, its action word, the sentence a tap sends, and its source) and one count line. It reads the brief Well already built this morning and builds nothing new. Use it when the person asks for their brief or what their brief said today.

status is ok with brief set; no_brief_routine when the person has no morning brief in this workspace; no_brief_today when no brief was built in the last 24 hours; failed when the read failed. A card with no point is a calm day: say so in one line.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
briefYes
statusYes
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
brief_started_atYesWhen the run that built the brief started, ISO 8601.
resolved_workspaceYes
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the readOnly/destructive annotations: it discloses the four terminal statuses (ok, no_brief_routine, no_brief_today, failed) with the condition for each, states that the read never creates anything, and specifies agent behavior for an empty card ('a calm day: say so in one line'). That is behavioral context the agent could not infer from annotations or schema.

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?

Front-loaded with what is returned, then usage, then statuses, then workspace mechanics — a logical order with no filler. It is long for a read tool and the workspace paragraph partly restates the schema, which keeps it from a 5.

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?

With an output schema present, the description still carries the status vocabulary, the empty-brief instruction, and the multi-workspace routing rule. Nothing an agent needs to call this correctly and narrate the result is missing.

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 100%, so the baseline is 3. The description echoes the workspace_id rule already spelled out in the schema and says nothing about conversation_id or the workspace_scope enum, so it adds little parameter meaning beyond the structured fields.

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 ('reads the brief Well already built this morning') and enumerates the payload it returns: title, at most 3 points with their fields, and one count line. The explicit 'builds nothing new' separates it from any generation or write path, so an agent can identify it without opening the schema.

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?

Names the triggering condition precisely: 'Use it when the person asks for their brief or what their brief said today.' It also routes the workspace decision (call directly when one workspace is authorized, pass workspace_id when several). It stops short of naming a when-not scenario or an alternative sibling tool such as a from-scratch brief builder.

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