A2Me MCP Server

Find family member

find_family_member

Read-onlyIdempotent

Search for a family member by name or relationship, such as 'Sarah' or 'my grandmother', to access their profile.

Instructions

Searches for a family member by name or relationship. Supports "my grandmother", "mom", "Sarah".

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": "find_family_member"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Name, relationship, or natural reference (e.g., "Sarah", "my grandmother")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 14, 2026

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 destructiveHint=false, covering the safety profile. The description adds the behavioral trait that it accepts natural language references, which is useful, but it doesn't disclose return behavior or edge-case handling. With annotations covering safety, the moderate score reflects incomplete behavioral context.

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 two sentences long, front-loads the action ('Searches for...'), and includes concrete examples. Every sentence contributes meaning without redundancy or fluff.

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 one-parameter search tool with strong annotations, the description covers core functionality and expected inputs. However, since there is no output schema, it would be more complete to mention what the tool returns (e.g., a person object) or any limitations. Still, the current description is largely sufficient for this simple case.

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%, and the query property description already includes the same examples ('Sarah', 'my grandmother') as the tool description. The description adds no new parameter semantics beyond what the schema provides, so it meets the baseline but doesn't go further.

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 'searches for a family member' using a specific verb and resource, and specifies the query types ('by name or relationship'). This differentiates it from siblings like get_family_members, which likely lists all members, and get_person_profile, which fetches a known person's details.

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 implies when to use the tool by showing example queries ('my grandmother', 'mom', 'Sarah'), but it doesn't explicitly contrast with alternative tools or state when not to use it. The context is clear enough for an agent to infer the primary use case, but exclusions are missing.

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

Deploy Server