Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Folder stats

get_stats
Read-onlyIdempotent

Shows where your life-admin folder is and summarizes item counts by type, overdue items, and items due in the next 30 days so you can orient at the start of a conversation.

Instructions

Where the life-admin folder lives and what it holds: item counts by type, how many are overdue and how many are due in the next 30 days. Call once at the start of a conversation to orient.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the payload shape it discloses: location, counts by type, overdue, and 30-day due counts. That is genuinely useful behavioral detail, and the 'call once' guidance implies it is a cheap orienting read; it does not mention cost, freshness, or empty-state behavior.

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, no filler: the first enumerates the return contents and the second states the invocation pattern. Both lead with the information an agent needs to decide to call it.

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?

With no output schema, the description carries the burden of describing the return value, and it does so at a reasonable level of specificity for a parameterless stats tool. Slight gaps remain, such as whether the 30-day window is fixed and whether counts come from a cached snapshot, but nothing prevents a correct call.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter detail is needed or missing.

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 names the specific resource (the life-admin folder) and enumerates what the result contains: item counts by type, overdue count, and due-within-30-days count. That is far more than a restatement of the name, though it does not explicitly contrast itself with siblings such as due_soon or list_items, leaving an agent to infer the difference.

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?

"Call once at the start of a conversation to orient" gives a clear temporal trigger and an implicit frequency cap (once). It stops short of stating when not to use it or naming which sibling to call instead for detail, so it is clear context without explicit alternatives.

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