A2Me MCP Server

Get recent family activity

get_recent_family_activity

Read-onlyIdempotent

Retrieve recent family updates including posts, photos, videos, birthday cards, and events to answer questions or compose messages.

Instructions

Returns recent family activity (posts, photos, videos, birthday cards, events).

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max results (default: 20)
`sinceHours`	No	Hours to look back (default: 72)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 14, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the content scope (posts, photos, etc.) but does not disclose behavioral details such as ordering, time-window defaults, or whether results are paginated. The added value over annotations is modest, so a 3 is appropriate.

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?

The description is a single, clear, front-loaded sentence with no redundant words. It efficiently states the tool's output without rambling, earning a top score for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with rich annotations and complete schema, the description is adequate but not fully complete. It lacks differentiation from many sibling tools and does not mention return format or pagination. Given the absence of an output schema, a bit more context would improve completeness, but the description is minimally viable.

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% for the two parameters (limit and sinceHours), so the structured schema carries full semantic weight. The description adds no parameter-specific meaning, which is acceptable given the high schema coverage, yielding the baseline score of 3.

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 clearly states the verb (returns) and resource (recent family activity) with specific content types (posts, photos, videos, birthday cards, events). It is specific enough to convey the tool's purpose, though it does not explicitly differentiate from sibling tools like 'whats_new' or 'get_upcoming_events'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. Given siblings like get_upcoming_events and whats_new, the description lacks any contextual cues or exclusions to help an agent choose this tool over similar ones.

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

Deploy Server