Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Due soon

due_soon
Read-onlyIdempotent

Lists overdue items, items due within a specified number of days, and items whose reminder window has opened, sorted by due date and showing today's date.

Instructions

What needs attention: overdue items, items due within the next days days, and items further out whose reminder window has already opened (e.g. a passport with a 180-day reminder). Sorted by due date, with today's date stated. This is the main 'what's coming up?' tool.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow far ahead to look (default 30)
typeNoOnly items of this type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavior: results are sorted by due date and today's date is echoed back, plus the non-obvious rule that items beyond the horizon can still appear if their reminder window opened.

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?

Two sentences, front-loaded with the inclusion criteria and finished with a positioning statement. The parenthetical example is the only elaboration and it directly resolves an otherwise confusing rule, so nothing is wasted.

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 zero-required-parameter read tool with full schema coverage and no output schema, the description covers scope, ordering, and the date echo. The one remaining gap is the shape of an individual item, which an agent must discover at call time since no output schema exists.

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 both `days` and the type enum are already documented in structured form, which sets the baseline at 3. The reminder-window explanation slightly enriches what `days` actually bounds (it is not a hard cutoff), but no format or edge-case detail beyond the schema is given.

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 concrete retrieval task and enumerates its scope precisely: overdue items, items due within `days`, and items whose reminder window has opened. The passport example makes the third category unambiguous, and the closing line positions it against the broader catalog as the primary 'what's coming up?' tool.

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

Usage Guidelines3/5

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

Calling itself 'the main what's coming up? tool' gives a default preference, and the enumerated inclusion criteria imply that a plain inventory request belongs elsewhere. However, it never names an alternative (list_items, search_items, money_ahead) or states an explicit when-not condition, so routing still requires inference.

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