Skip to main content
Glama
Sign In
mindin

mindin

by gronare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

backlog

Lists notes sorted by priority then age from an Obsidian-style vault, with optional area and priority filters and a result limit.

Instructions

CHEAP — the backlog sorted by priority then age. Filter by area (a stem, or the prefix a family of stems shares) and by priority.

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

Input Schema

NameRequiredDescriptionDefault
areaNo
limitNo
priorityNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the sort order and that the operation is cheap, plus some area-filter semantics, but it does not state that this is a read-only query, whether filters are optional, or any permission/rate-limit context.

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 front-loaded sentence: cost signal first, then resource and ordering, then filters. It is compact and every clause contributes useful information.

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

Completeness3/5

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

An output schema exists, so return values need not be described. Still, for a three-parameter query tool with 0% schema coverage, the definition should say more about the limit parameter and priority values, and ideally clarify its read-only nature.

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

Parameters2/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 compensate for all three parameters. It explains 'area' well (stem or shared prefix) and mentions 'priority' as a filter, but gives no accepted priority values and never mentions 'limit', leaving key parameter meaning undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (the backlog) and its ordering (priority then age), and the filters distinguish it from backlog_add. However, it omits an explicit verb such as list or retrieve, so the purpose is clear but not maximally specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'CHEAP' hints at using this over a costlier alternative, but no sibling is named and there is no explicit when-to-use or when-not-to-use guidance. The filtering instructions explain how to call it, not when it should be chosen over search, list_files, or backlog_add.

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