Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

List items

list_items
Read-onlyIdempotent

Retrieve tracked bills, renewals, subscriptions, and other life-admin items, optionally filtered by type and sorted by due date. Use it to review upcoming deadlines and undated tasks.

Instructions

List tracked items, optionally filtered by type, sorted by due date (undated items last).

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly items of this type
limitNoMaximum number of items (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is fully covered. The description adds one genuinely useful behavioral detail not in the schema — results are sorted by due date with undated items last — but says nothing about permissions, result size behavior, or what 'tracked' excludes (e.g. deleted items).

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?

One sentence, front-loaded with the action and resource, with the two qualifying clauses (optional filter, sort order) packed in without filler. Nothing needs trimming.

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 two-parameter, fully annotated read-only tool with complete schema coverage, the definition covers action, filtering, and ordering adequately. It stops short only on return-shape hints and on routing versus the similar search_items sibling.

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 description coverage is 100%, so both parameters (type enum and limit with default 100) are already documented in the schema. The description's 'optionally filtered by type' restates the schema rather than adding format or semantics beyond it.

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?

A specific verb+resource ('List tracked items') plus the filtering dimension and output ordering. It does not, however, distinguish itself from the sibling search_items, so an agent must infer which listing path to take.

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?

There is no explicit when-to-use guidance, no exclusion of alternatives, and no mention of siblings such as search_items or due_soon. The only steer is 'optionally filtered by type', which describes a parameter rather than a usage condition.

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