Skip to main content
Glama

index_brain

Indexes new or changed Markdown notes into a knowledge graph by extracting entities and relations with the configured model CLI. Returns a remaining count; repeat until zero, or use force to reindex all.

Instructions

Read notes that are new or have changed and add their entities and relations to the graph, using the configured model CLI. The result includes a remaining count; repeat the call until it is 0. force=true processes every note again.

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

Input Schema

NameRequiredDescriptionDefault
forceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose that indexing uses a configured model CLI, that the result carries a remaining count requiring repeated calls, and that force replays every note. It omits whether force=true duplicates or overwrites existing graph entries, whether the operation is idempotent, and any cost or failure behavior for an LLM-backed batch job.

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 short sentences, front-loaded with the action and ending with the parameter detail; no filler. The opening clause 'Read notes that are new or have changed' is slightly awkward but not wasteful.

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?

For a one-parameter tool with no output schema and no annotations, the definition covers the core loop and force semantics. It leaves a meaningful gap around what happens to pre-existing graph data on re-index and on failure mid-batch, which matters for a mutation tool with no safety annotations.

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 0% and the single parameter is undocumented in the schema, so the description has to compensate. It does: 'force=true processes every note again' defines the default-versus-forced distinction, which is the only semantic an agent needs here.

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 states a concrete verb and resource: read new/changed notes and add their entities and relations to the graph. That is specific enough to distinguish it from read-only siblings like search_brain or query_notes, though it never names a contrasting tool explicitly.

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?

It gives an operational loop rule ('repeat the call until it is 0') and when to use force=true, which is real guidance. It does not say when NOT to re-index, nor how this differs from adjacent tools such as consolidate_graph or organize_vault.

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