Skip to main content
Glama
Sign In
mcp-server-decisions

mcp-server-decisions

by Roberton003
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

query-decisions

Search prior decisions by keyword, technology, or domain to find relevant architectural decisions.

Instructions

Search prior decisions by keyword, technology, or domain

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": "query-decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoPartial domain filter
keywordNoSearch in problem + solution + alternatives (case-insensitive)
technologyNoExact technology filter (e.g., 'duckdb')
max_resultsNoMaximum results to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only states 'search' without disclosing behavioral traits like read-only, pagination, or authentication requirements.

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 a single concise sentence with zero waste, efficiently conveying the tool's purpose and core dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 4 parameters and no output schema, the description lacks details about return format, filter interaction, or sorting. More context is needed for a search tool.

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 coverage is 100%, so the input schema already fully describes each parameter. The description adds no additional semantic meaning beyond the schema.

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 clearly states the verb 'search' and the resource 'prior decisions', listing the search dimensions (keyword, technology, domain). This distinguishes it from sibling tools that record decisions, predictions, and outcomes.

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?

The description implies usage for searching past decisions, contrasting with recording siblings. However, it does not explicitly state when not to use or mention alternatives.

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