Skip to main content
Glama

LovedOne Family MCP

List Care Events

list_care_events
Read-onlyIdempotent

Returns recent care events for the caller's family workspace. Optionally scope to a single lovedOneId; otherwise aggregates across all loved ones on the workspace. Limit is 1-50 and is applied per loved one when aggregating.

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_care_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax events to return (1-50, default 20). Applied per loved one when lovedOneId is omitted.
lovedOneIdNoOptional. Restrict results to one loved one. Must belong to the caller's workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: workspace-level scoping and the fact that limit is applied per loved one when aggregating. Gaps remain around result ordering and what 'recent' means chronologically.

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?

Three short sentences, front-loaded with purpose, then scoping mode, then the limit constraint. No redundant or filler text.

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?

Complete enough for correct invocation given the rich schema and annotations. However, with no output schema and no description of return shape or ordering, an agent cannot anticipate what a 'recent care event' record contains or how results are sorted.

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 are already documented, including the default and the per-loved-one limit behavior. The description restates rather than extends that information, so baseline 3 applies.

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 and resource ('Returns recent care events') plus the scoping domain ('caller's family workspace'). The name and description are unambiguous, and no sibling tool operates on care events, so differentiation is not needed.

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?

Explains the two usage modes clearly: scope to a single lovedOneId, or omit it to aggregate across all loved ones on the workspace. There is no explicit when-not or alternative-tool guidance, but for a list tool of this shape the mode selection is the key decision and it is spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.