Skip to main content
Glama
Sign In
A2Me MCP Server

A2Me MCP Server

by Kinnectd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get message context for person

get_message_context_for_person
Read-onlyIdempotent

Get personalized message context for a family member, with suggestions and privacy notes based on occasion and tone.

Instructions

Returns context for writing a message to a family member with suggestions and privacy notes.

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": {
      "personReference": "<personReference>"
    },
    "name": "get_message_context_for_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoDesired tone (e.g., "warm", "funny", "formal")
occasionNoOccasion (e.g., "birthday", "thank you")
personReferenceYesWho the message is for (name or relationship)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds output content (suggestions and privacy notes) but does not disclose further behavioral traits like data freshness, pagination, or filtering. This is adequate but not rich.

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 no redundant information. It efficiently communicates the tool's purpose and output.

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?

The tool is simple with 3 parameters and no output schema. The description adequately conveys the high-level return ('suggestions and privacy notes'), and the schema covers inputs. It could benefit from a bit more detail on what 'context' includes, but it is complete enough for this moderate complexity.

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%, and all three parameters (personReference, tone, occasion) are well-described in the schema. The description adds no additional parameter-specific meaning, so the baseline of 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?

The description uses a specific verb ('Returns') and resource ('context for writing a message to a family member'), clearly distinguishing this from sibling tools like get_person_profile or get_birthday_card_context by mentioning 'suggestions and privacy notes'. It states exactly what the tool provides and for whom.

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?

The description clearly implies when to use: when writing a message to a family member. However, it does not explicitly mention alternatives or exclusion criteria, 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.

Deploy Server

Other Tools