Skip to main content
Glama
MnemeHQ

Mneme Decision MCP

Official
by MnemeHQ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search proposals and canonical decisions

decision.search
Read-onlyIdempotent

Search architectural decision records by text or exact metadata filters. Returns proposals and canonical decisions in separate, never-merged lists, with read-only access.

Instructions

Deterministic text/exact-metadata search. Proposals (lifecycle proposed/accepted/rejected) and canonical decisions (lifecycle active/superseded/deprecated/inactive) are returned in separate lists and never merged. Read only: this tool never mutates any state. Search rank has no enforcement meaning. Use decision.get when you already have a stable id. Within each record domain, all applicable filters combine with AND semantics; proposal-only filters do not exclude canonical results, and vice versa.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoCase-insensitive substring matched against supported proposal and canonical text fields. Empty matches all records.
producer_nameNoOptional exact producer-name filter on proposal provenance; does not filter canonical decisions.
proposal_statusNoOptional exact proposal lifecycle filter; applies only to the proposals result list.
source_referenceNoOptional exact source-reference filter on proposal provenance; does not filter canonical decisions.
origin_classificationNoOptional exact origin-classification filter on proposal provenance; does not filter canonical decisions.
canonical_lifecycle_statusNoOptional exact canonical lifecycle filter; applies only to the canonical_decisions result list.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.9.2
    • addedInput schema / properties / canonical_lifecycle_status / description
      Added value: +"Optional exact canonical lifecycle filter; applies only to the canonical_decisions result list."
    • addedInput schema / properties / origin_classification / description
      Added value: +"Optional exact origin-classification filter on proposal provenance; does not filter canonical decisions."
    • addedInput schema / properties / producer_name / description
      Added value: +"Optional exact producer-name filter on proposal provenance; does not filter canonical decisions."
    • addedInput schema / properties / proposal_status / description
      Added value: +"Optional exact proposal lifecycle filter; applies only to the proposals result list."
    • addedInput schema / properties / query / description
      Added value: +"Case-insensitive substring matched against supported proposal and canonical text fields. Empty matches all records."
    • addedInput schema / properties / source_reference / description
      Added value: +"Optional exact source-reference filter on proposal provenance; does not filter canonical decisions."
  2. First observedv0.9.1

TDQS

A5/5.0
Behavior5/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, and the description adds non-redundant behavioral detail: deterministic results, no merging of result domains, no enforcement meaning for search rank, and AND semantics for combined filters. No statement contradicts the annotations.

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 compact, front-loaded with the core search behavior, and every sentence adds actionable information. There is no filler or repetition of the title/schema.

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 multi-domain search tool with six optional filters, the description covers identity, scope, result separation, read-only safety, filter semantics, rank behavior, and routing to the stable-id alternative. The presence of an output schema covers return-structure details that would otherwise be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description still adds important parameter behavior beyond the schema: 'all applicable filters combine with AND semantics' and 'proposal-only filters do not exclude canonical results, and vice versa.' This materially changes how an agent should interpret the optional filters.

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 names a specific operation (deterministic text/exact-metadata search) over two clearly defined record domains, proposals and canonical decisions, and explicitly notes they are returned in separate lists and never merged. This disambiguates the tool from siblings like decision.get and decision.propose.

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 an explicit routing rule: 'Use decision.get when you already have a stable id.' The read-only statement and filter-scoping semantics also imply when this tool is appropriate and clarify what it does not do.

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