Skip to main content
Glama
Sign In
big-brain

big-brain

by jzhao234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Log to the daily note

daily_log

Append timestamped entries to today's daily note Log section to capture decisions, progress, and events as they happen, creating a work journal.

Instructions

Append a timestamped entry to today's daily note Log section. Use to record decisions, progress, and events as they happen — this builds the user's work journal.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "daily_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesWhat happened / what was decided

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. It usefully discloses append (additive, non-destructive) semantics and the automatic timestamp, but says nothing about whether the daily note is created if it is missing, ordering, or failure behavior — notable gaps for a write tool with zero annotation coverage.

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 tight sentences with the action and target front-loaded and the intent trailing; nothing is redundant or padded.

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?

For a one-parameter append tool with no output schema, the description covers what gets written and where. The remaining gap is mutation-side behavior (note creation on miss, error handling) that would matter more given the complete absence of annotations.

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% for the single "text" parameter, so the baseline is 3. The description reframes the field as "decisions, progress, and events," adding only marginal meaning beyond the schema's "What happened / what was decided."

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 ("Append") and a precise resource ("today's daily note Log section") with the "timestamped" qualifier, which separates it from the generic append_note sibling. It stops short of naming that sibling explicitly, so differentiation is inferable rather than stated.

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?

"Use to record decisions, progress, and events as they happen" gives a clear situational context for when to reach for this tool. It offers no exclusions or named alternatives (e.g., vs. append_note or capture), which keeps it out of the top band.

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

Deploy Server

Other Tools