Skip to main content
Glama

Get account map summary

get_account_map_summary
Read-only

Buying-committee coverage for one account. Returns, per influence role (economic_buyer, executive_sponsor, champion, technical_evaluator, business_evaluator, finance, procurement, legal, security), a state (REACHABLE = someone holds the role and we have a warm path; FOUND_NO_PATH = people hold the role but none is reachable; GAP = nobody found), found_count and reachable_count, plus totals (committee_people, reachable_people, roles_reachable, roles_found_no_path, roles_gap) and the account header.

Use when: Use for 'who is on the buying committee at <account>', 'which committee roles have no warm path' or 'how well covered is <account>'. Start here, then call get_account_map_people to name the people behind a role. Needs the internal account UUID: resolve the account first with search_accounts_with_filters. For warm paths into an account without the committee view use get_warm_intro_paths_by_account.

Behavior: read_only

workspace_id / user_id are injected from request headers.

Returns roles[] with fields:

key label state found_count reachable_count Also returns pagination info (committee_people, reachable_people, roles_reachable, roles_found_no_path, roles_gap).

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

Input Schema

NameRequiredDescriptionDefault
path_ruleNo
account_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it defines the three state values (REACHABLE, FOUND_NO_PATH, GAP) precisely and discloses that workspace_id/user_id are injected from headers, which affects how the caller should build arguments. It also adds a non-obvious operational constraint about presenting multiple results rather than acting automatically.

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?

Front-loaded and clearly sectioned (purpose, use-when, behavior, returns), but the return fields are enumerated twice — once inline per role and again in a bulleted 'Returns roles[] with fields' block — which is redundant given an output schema exists.

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 read-only summary tool with an output schema, the description covers purpose, sequencing, prerequisites, and state semantics thoroughly. The only material gap is the unexplained path_rule parameter, which an agent cannot infer from either schema or prose.

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% for two parameters. The description clarifies account_id as the internal account UUID and how to obtain it, but path_rule is never mentioned and both params default to null with no explanation of what null means or what path_rule controls.

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 opening line names a specific resource and scope: 'Buying-committee coverage for one account.' It immediately distinguishes this from get_account_map_people (people behind a role) and get_warm_intro_paths_by_account (warm paths only), so an agent can choose without opening schemas.

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 explicit 'Use when' triggers with quoted example questions, a sequencing rule ('Start here, then call get_account_map_people'), a prerequisite (resolve the account UUID via search_accounts_with_filters), and a stated alternative for the no-committee 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