Skip to main content
Glama
Sign In
A2Me MCP Server

A2Me MCP Server

by Kinnectd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get birthday card context

get_birthday_card_context
Read-onlyIdempotent

Obtain personalized context for writing birthday cards, including recipient interests, memories, and tone suggestions.

Instructions

Returns context for writing a birthday card — recipient's interests, memories, and tone suggestions.

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": {
      "personId": "<personId>"
    },
    "name": "get_birthday_card_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesPerson ID of the birthday card recipient

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, idempotentHint, and non-destructive behavior, covering safety. The description adds what content is returned (interests, memories, tone suggestions) but does not disclose behaviors like empty results or data source. 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?

The description is a single, concise sentence that conveys the core purpose without any redundant or unnecessary wording. It is well-structured and front-loaded with the main action.

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 read-only tool with one parameter and no output schema, the description is largely complete. It explains the purpose and the nature of the returned context. It could mention edge cases like missing person data, but overall it is sufficient.

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?

The schema fully describes the only parameter (personId) with a meaningful description, so schema coverage is 100%. The description does not add any additional parameter context beyond the schema, 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?

The description clearly states the tool returns context for writing a birthday card, listing specific content types (interests, memories, tone suggestions). This distinguishes it from sibling tools like get_message_context_for_person by being birthday-specific.

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 implicitly conveys use when writing a birthday card, giving clear context. However, it does not explicitly compare with alternatives or state when not to use it, so it lacks explicit exclusions.

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