Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Search items

search_items
Read-onlyIdempotent

Search saved bills, renewals, warranties, and documents by keywords to find the right record and avoid adding duplicates.

Instructions

Find items whose title, provider, tags or notes contain any of the words in the query, best matches first. Use before add_item to avoid duplicates, and for questions like 'where's the boiler warranty?'.

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": {
      "query": "<query>"
    },
    "name": "search_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly items of this type
limitNoMaximum results (default 10)
queryYesA few keywords, e.g. 'boiler warranty'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/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 covered. The description adds meaningful behavior beyond that: matching is per-word across four fields and results are ordered by relevance, which affects how an agent should phrase queries. It does not describe what a result record contains or how an empty result behaves.

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 tight sentences with no filler: the matching and ranking rule comes first, then the practical usage triggers. Every clause carries information an agent would act on.

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 read-only, three-parameter search tool with full schema coverage and no output schema, the definition covers matching semantics, ordering and typical triggers. The remaining gap is that it never hints at what a returned item looks like, which slightly limits downstream use.

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 the schema already documents query, type enum and limit with defaults. The description adds only the OR-semantics nuance ('any of the words'), which is marginally useful but not a substitute for extra detail on the type filter or limit behavior.

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 specific verb and resource ('Find items') and defines the searchable fields (title, provider, tags, notes) plus ranking ('best matches first'). This clearly separates it from list_items, which would enumerate rather than keyword-search.

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?

It gives concrete when-to-use triggers: before add_item to check for duplicates, and for natural-language recall questions like 'where's the boiler warranty?'. It names one sibling explicitly but offers no when-not guidance (e.g., use list_items to browse everything), so it falls short of a 5.

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