Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Open home screen

open_home_screen
Read-onlyIdempotent

Open a local home screen in the browser showing upcoming dates, next payday and bills, weekly spending and savings, with a Print button; works only on this computer while the session is open.

Instructions

Open the person's home screen in their web browser: what's coming up, the next payday and the bills before it, this week's spending and the rainy-day pot, in large, calm print with a Print button. It runs only on this computer, and stays available while this assistant session is open.

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

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 declare readOnly, idempotent, non-destructive and not open-world, so safety is covered. The description adds genuinely new behavioral context: the output is rendered in the local web browser, it is local-machine only, and its availability is tied to the lifetime of the assistant session. It does not say what happens on repeat calls, but idempotentHint already covers that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and its result. The list of screen contents is slightly long but each element tells the agent what the user will actually see, so it earns its place; the session-lifetime caveat is a useful closing note.

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 parameters, no output schema and full annotation coverage, the description carries the remaining burden and does so: it describes the rendered output, the local/browser constraint and the session-bound lifetime. Only the repeat-invocation behavior is left implicit, which the annotations handle.

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 no parameters, so the baseline is 4 and there is nothing further the description could add on this dimension.

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?

States a specific verb (open) and resource (the person's home screen in their web browser) and then enumerates exactly what that screen contains: upcoming items, next payday and preceding bills, this week's spending, rainy-day pot. No sibling tool does anything comparable, so an agent can distinguish it immediately.

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?

The description implies usage (an at-a-glance, printable overview for the person) and states a real constraint — it runs only on this computer and only while the assistant session is open. It never says when to choose this over e.g. spending_summary or money_ahead, nor any exclusions, so guidance is implied rather than explicit.

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