Skip to main content
Glama

Load core second-brain context

second_brain_core_context
Read-only

Returns the compact core-principles context used by the SessionStart hook so AI clients can initialize memory and session workflows from the local knowledge vault.

Instructions

Return the compact core-principles context used by the SessionStart hook.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
contextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the payload is 'compact' and sourced from a session-start hook, but says nothing about whether it is static, cacheable, or how it relates to other context tools; an output schema covers return values.

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?

A single front-loaded sentence with no redundant wording or filler. It is efficient, though its brevity leaves the central concept ('core-principles context') undefined rather than merely compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters, an output schema, and read-only annotations, most structured burden is already handled, so the description only needs light context. It still leaves unclear what the 'core-principles context' contains and how an agent should use it relative to the ten sibling tools.

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 the schema carries no semantics to explain and the description has nothing to compensate for. Baseline 4 applies; no parameter-level claims are made or needed.

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 and resource ('Return the compact core-principles context'), which is more informative than the title alone. However, 'core-principles context' is defined only by reference to an internal 'SessionStart hook', and nothing distinguishes it from siblings like second_brain_read or second_brain_recall_experience.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'used by the SessionStart hook' implies session-bootstrap usage but never instructs the agent to call it, nor names an alternative for fetching context mid-session. Usage is inferred rather than stated, with no exclusions or when-not conditions.

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