Skip to main content
Glama

Get account map person

get_account_map_person
Read-only

Full detail for one person on an account map: profile (title, seniority, department, influence roles), every kept warm path best first (teammate, strength, path types, relationship chain, summary, confidence, intro_value, reasoning, evidence) and likely managers (reports_to_candidates). The first path is the best way in.

Use when: Use for 'best way in to <person>' or 'how do we reach <person>' once you have the person's person_key from get_account_map_people. Do not guess person_key. For a person outside an account map use get_warm_intro_paths_by_contact.

Behavior: read_only

workspace_id / user_id are injected from request headers.

Returns paths[] with fields:

teammate_user_id teammate_name strength path_types chain summary confidence intro_value reasoning score work_overlap_high_value evidence Returns reports_to_candidates[] with fields: person_key full_name title seniority department influence_roles Also returns pagination info (person_key, full_name, title, linkedin_url, seniority, department, influence_roles, influence_roles_source, contact_id, avatar_url).

IMPORTANT: If the response contains more than one record, always present the options to the user and ask them to choose before taking any follow-up action. Do not act on all results automatically.

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

Input Schema

NameRequiredDescriptionDefault
path_ruleNo
account_idNo
person_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered before the description starts. The description adds genuine value beyond that by noting header-injected workspace_id/user_id (explaining their absence from the schema) and by warning that multi-record responses must be presented to the user for a choice rather than acted on. The 'Behavior: read_only' line merely restates the annotation, and the long return-field catalogue duplicates the output schema rather than disclosing new behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and usage blocks are well front-loaded and tight. However, the bulk of the text is a field-by-field dump of return values that an output schema already supplies, which bloats the definition without helping an agent decide or call correctly. The trailing IMPORTANT rule is clear and earns its place.

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 read-only lookup with a full output schema, the description does not need to enumerate return fields, yet it spends most of its length doing so while leaving two of three input parameters unexplained. The guidance on choosing between this and the sibling tools is complete, so the main residual gap is the undocumented account_id and path_rule semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, but it only explains person_key (must come from get_account_map_people, not guessed). Neither account_id nor path_rule is mentioned anywhere, and path_rule's meaning and valid string values are left entirely opaque despite being the only non-obvious control on path selection.

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 ('Full detail for one person on an account map') and enumerates what the detail contains: profile, kept-warm paths ordered best-first, and reports_to_candidates. It also distinguishes itself from get_account_map_people (source of person_key) and get_warm_intro_paths_by_contact (for people outside an account map).

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

Usage Guidelines5/5

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

Provides an explicit 'Use when' trigger with example phrasings ('best way in to <person>', 'how do we reach <person>'), a prerequisite (obtain person_key from get_account_map_people), an explicit prohibition ('Do not guess person_key'), and a named alternative for the out-of-scope case.

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.

Resources