Skip to main content
Glama

get_briefing

Retrieves a session briefing covering available sources, user context, open action items, projects, goals, recent coding work, and recent timeline. Check it before asking about past work or decisions.

Instructions

Call this first in every session. Returns what LokalBot knows that this session may use: which sources are available, what the user shared about themselves, their open action items, current projects and goals, recent coding-agent work, and a timeline of recent days, weeks, and months. Check it, and search LokalBot, before asking the user about past work or decisions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the return content in real detail rather than restating the name. 'Returns' implies a read-only operation and no side effects, and the breadth of categories warns the agent that the payload is broad. Gaps remain: no statement of permission scoping, payload size/latency, or whether the snapshot is cached or live, which matters for a call mandated at the start of every session.

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 sentences, both earning their place, with the imperative 'Call this first in every session' front-loaded before any detail. The long content enumeration is dense but necessary given there is no output schema to reveal what comes back, and the closing sentence adds a distinct usage rule rather than repeating the first.

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 annotations, no output schema, and no parameters, the description is the only source of truth about the return value, and it covers the contents thoroughly enough to act on. What it leaves unstated is the practical shape of the response — volume, filtering limits (none available), and freshness — which an agent deciding whether to re-call it mid-session would want.

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 zero parameters, so there is no parameter meaning for the description to add; the baseline of 4 applies. The description correctly avoids inventing arguments, though it also never says explicitly that the call is unfiltered and always returns the whole snapshot.

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?

The description pairs a clear retrieval verb with an explicit enumeration of the resource contents: available sources, user-shared personal context, open action items, current projects and goals, recent coding-agent work, and a recent-days/weeks/months timeline. The opening 'Call this first in every session' immediately separates it from the item-level siblings like get_action_items, get_personal_context, or get_timeline, which serve one slice of this aggregated view. An agent can identify this as the session orientation call without opening any 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?

Timing guidance is unusually explicit ('Call this first in every session') and it adds a behavior rule: check this and search before asking the user about past work or decisions. What is missing is any when-not or named alternative — 'search LokalBot' is generic rather than pointing at ask_library or search_files, and nothing says when to skip this call. Still, the ordering constraint is stronger than most definitions provide.

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