Skip to main content
Glama

Load the owner's identity and standing context

brain_identity
Read-onlyIdempotent

Retrieves the vault owner's identity, preferences, active projects, and recent activity at the start of a conversation, optionally narrowed by topic, so the assistant can adopt it as working context.

Instructions

Call this FIRST in every conversation. Returns who the owner is, their preferences and feedback rules, the projects they run, and what they touched recently. Adopt it as your persona and working context. Captured facts are only the ones true now; brain_facts has their history. Pass topic (a few words about what the conversation is about) to get a smaller bundle with only the memory notes that apply.

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

Input Schema

NameRequiredDescriptionDefault
topicNoWhat this conversation is about, e.g. 'interview prep' or 'database backups'. Omit for the full bundle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses that the bundle should be adopted as persona and working context, that captured facts are current-only, and that passing topic returns a smaller bundle with only applicable memory notes. These are meaningful behavioral traits not captured by 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the critical instruction to call it first, then explains returns, usage posture, sibling distinction, and parameter effect. Every sentence is useful and appropriately sized for a one-parameter startup tool.

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?

For a simple, optional-parameter, read-only tool with annotations and no output schema, the description covers purpose, expected return content, ordering requirement, persona adoption, historical-facts alternative, and topic behavior. Nothing essential is missing.

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?

Schema coverage is 100%, so the schema already documents topic and the omit-for-full-bundle behavior. The description adds useful semantic detail by clarifying that topic is a few words about the conversation and that it narrows the result to applicable memory notes.

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 specifies a clear verb and resource: load the owner's identity and standing context. It enumerates the returned content (owner identity, preferences, feedback rules, projects, recent activity) and explicitly distinguishes itself from brain_facts by noting that brain_facts holds historical facts.

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

Usage Guidelines5/5

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

It gives a direct usage rule: 'Call this FIRST in every conversation.' It also states when to use the optional topic parameter and implies the alternative for historical facts by naming brain_facts.

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