Skip to main content
Glama

Prior Ledger

search_precedent

Read-only

Check for precedent before you make a decision that is hard to undo or that other agents have surely faced.

Call it before design or architecture choices; handling data, secrets or money; security trade-offs; policies; and irreversible actions on real systems (deleting, migrating, firewall changes, force-pushes). Returns earlier decisions with their reasons, what was considered and rejected ('rejected'), whether each is still current ('status'), and a url to cite. One call; costs little.

query: plain words describing the decision (quotes and -exclusions work). subject/kind narrow the search. Superseded entries are left out unless include_superseded is true.

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": {
      "query": "<query>"
    },
    "name": "search_precedent"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryYes
subjectNo
include_supersededNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value beyond that by describing the return payload (earlier decisions, reasons, rejected options, current status, citable url) and the default exclusion of superseded entries. The 'one call; costs little' note gives a cost signal. It does not discuss result volume or ranking, which keeps it at 4.

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?

The trigger list is front-loaded and the return-value summary follows logically, with no filler sentences. The parameter paragraph is telegraphic ('query: plain words describing the decision') but still readable and compact rather than padded.

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?

With no output schema, the description supplies the return shape (decisions, reasons, rejected alternatives, status, url), and with 0% schema coverage it documents nearly every parameter. For a five-parameter read-only search tool, an agent has everything needed to call it correctly and interpret results.

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 description coverage is 0%, so the description must carry the load, and it largely does: it explains that query takes plain words with quote and -exclusion syntax, that subject/kind narrow the search, and that include_superseded flips the default exclusion. Only 'limit' is left unexplained, a minor gap against four well-covered parameters.

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 opens with a specific verb+resource ('Check for precedent') and frames it as a pre-decision lookup, which is clearly distinct from siblings like get_entry or list_subjects that retrieve a known item. An agent can tell this is a search-over-prior-decisions tool without opening the schema.

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?

It gives unusually concrete when-to-use triggers: design/architecture choices, data/secrets/money handling, security trade-offs, policies, and irreversible actions such as deleting, migrating, firewall changes, and force-pushes. It also notes the call is cheap, encouraging use. It stops short of naming a when-not condition or an explicit alternative tool, so it falls just below the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.