Skip to main content
Glama

Current decisions

current_decisions
Read-onlyIdempotent

Retrieve the decisions currently in force for a project, newest first, so you can check what was already decided before changing direction.

Instructions

The decisions in force for a project, newest first: every decision in Second Brain that no newer one supersedes. Read this before changing direction on something the user already decided.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many (default 50, at most 100).
projectNoThe project's name (the repository folder's name). Omit for the repository this server was started in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing supersession semantics (only non-superseded decisions are returned) and newest-first ordering, but says nothing about result size behavior or what a decision record contains.

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, zero filler, with the core definition front-loaded and the usage cue following. Every clause carries information.

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 two-parameter read tool with full schema coverage and rich annotations, the description supplies everything an agent needs: what is returned, in what order, and when to reach for it. No output schema is needed given the clear result semantics.

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%, so both parameters (limit, project) are already documented, including defaults and the omit-for-current-repo behavior. The description only implies project scoping and adds no format or syntax detail beyond the schema, so baseline 3 applies.

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?

States a specific resource (decisions in force for a project) with a precise scope qualifier — 'every decision in Second Brain that no newer one supersedes' — plus ordering ('newest first'). This is clearly distinguishable from memory-search siblings like search_memories or get_memory.

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?

Gives an explicit when-to-use trigger: 'Read this before changing direction on something the user already decided.' It does not name an alternative tool or state when not to use it, so it falls short of full routing guidance.

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