Skip to main content
Glama
Sign In
Align CLI

Align CLI

Official
by aligndottech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

align_get_related_decisions

Read-only

Retrieve prior decisions about a file or module across connected tools before editing to surface cross-tool context and avoid missing relevant constraints.

Instructions

BEFORE editing a file or module, call this to learn what was already decided about it across all the user's connected tools (not just code) - surfacing the cross-tool context an agent would otherwise miss. To answer a question about why something is the way it is, use align_ask instead.

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": {
      "file_path": "<file_path>"
    },
    "name": "align_get_related_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoWhat you are about to change, in plain words. Decisions are found by meaning, so a bare path finds little.
file_pathYesFile path or module name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the lookup spans all connected tools, not just code, and it is meant as a pre-mutation check. It stops short of saying what a result looks like or how many decisions come back.

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?

Two sentences, with the actionable trigger front-loaded in caps and the sibling routing at the end. The clause 'surfacing the cross-tool context an agent would otherwise miss' leans slightly rhetorical but does reinforce why the cross-tool scope matters.

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 two-parameter read-only lookup with no output schema, the description covers purpose, timing, source scope, and the sibling alternative. The only real gap is return shape, which an agent must discover by calling it.

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% and the schema itself explains the semantic-matching caveat for context ('a bare path finds little'), so the schema carries the parameter burden. The description adds no parameter-level detail beyond what is already structured. Baseline 3 is appropriate.

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 verb+resource (get related decisions about a file or module) and immediately scopes it: 'across all the user's connected tools (not just code)'. An agent can distinguish it from align_ask without opening either schema.

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?

Gives an explicit trigger ('BEFORE editing a file or module') and an explicit alternative with the condition that selects it ('To answer a question about why something is the way it is, use align_ask instead'). Both when-to-use and when-not-to-use are stated outright.

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