Skip to main content
Glama

Get the latest note

get_latest_briefing
Read-only

What the growth manager last wrote in a note for the active Space: the period it covers, its words as the Space's members read them, and the changes it recommended with their status. Returns 404 NO_BRIEFING when none has been written yet. Read-only. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.

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

Input Schema

NameRequiredDescriptionDefault
space_idNoOverride the active Space for this one call. Defaults to the active Space set via set_active_space (or GROWOMAT_SPACE_ID on the server). Pass to read/write a different Space without changing the session binding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation it discloses the empty-state contract (404 NO_BRIEFING when no note exists) and the Space-binding resolution order, which the agent cannot get from structured fields. It restates "Read-only" redundantly with the annotation, but that is harmless rather than contradictory.

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?

Three sentences, front-loaded with what you get, then the error case, then the scoping rule — no filler. The opening sentence is dense with a colon-list, but every item listed is a distinct part of the payload.

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 no output schema, the description must carry the return shape — and it does, naming the period, the note text, and the recommendations with statuses, plus the not-found case and the scoping default. Nothing an agent needs to decide to call it or interpret a 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 coverage is 100% and the single space_id parameter is fully documented in the schema, including the spc_ pattern and default resolution. The description's line about passing space_id to override merely echoes that, adding no new format or constraint detail.

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 names a specific resource (the growth manager's latest note for a Space) and enumerates its contents — period covered, prose, recommended changes with status — so an agent knows exactly what comes back. It does not differentiate against near-neighbours like get_answer_brief or list_open_loops, which is the only thing keeping it from a 5.

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 concrete operating context: the read is scoped to the active Space, set_active_space switches the binding, and space_id overrides for a single call. That is a clear when/how, though there is no explicit "use this instead of X" routing for the sibling read tools.

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