Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Get item

get_item
Read-onlyIdempotent

Retrieves full details for a titled life-admin item, including provider, cost, due date with days left, reminder start, reference, notes, and history.

Instructions

Full details of one item by title: provider, cost, due date with days left and when reminders start, reference, and its notes and history.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "<item>"
    },
    "name": "get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesThe item's title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile needs no restating. The description adds genuine value by enumerating the returned payload ('provider, cost, due date with days left and when reminders start, reference, and its notes and history'), effectively substituting for the absent output schema. It does not say what happens when the title does not exist or matches more than one item, which is a real gap for a title-keyed lookup.

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?

A single front-loaded sentence with the lookup key stated first and the return contents following; every clause names a distinct field and none is redundant. Nothing could be removed without losing information.

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 simple, fully annotated read tool with one documented parameter, the definition covers purpose, key, and returned fields well enough to call it correctly, and the field list compensates for having no output schema. The remaining omission is failure/ambiguity behavior on unknown or duplicate titles.

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% and the single 'item' parameter is already documented as 'The item's title', so the schema carries the burden. The description confirms the key is the title but adds nothing about matching semantics such as exactness, case sensitivity, or duplicate titles, leaving it at the baseline level.

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 states a specific verb and resource ('Full details of one item by title') and enumerates the exact contents returned (provider, cost, due date, reference, notes, history), so an agent immediately knows this is a single-record detail fetch rather than a list. It never names a sibling such as list_items or search_items, so differentiation is implied by 'one item by title' rather than stated.

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?

Usage is only implied: the phrasing 'one item by title' suggests the caller already knows the title, which implicitly routes title-unknown cases to search_items. There is no explicit when-to-use, no when-not, and no statement about alternatives, so the agent must infer the boundary itself.

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