Skip to main content
Glama

Vc Get Person

vc_get_person
Read-onlyIdempotent

Get one investing person by id: investing role, roles and firm history, companies, their own investments, and every contact route they published (email, LinkedIn, X, personal site), each with the page it was published on, the quoted text showing it, and whether it is a personal or a role address. Phone numbers and home addresses are never collected. People and their contact routes come from public sources, the firm's own site or the person's own published page. Anyone can request removal at support@pipeworx.io.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "person_id": "c0413f8e-57d4-4e1d-bfbf-15c479d0696f"
    },
    "name": "vc_get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_idYesPerson id, from vc_search_people, vc_get_investor partners, or relevant_partner

Output Schema

NameRequiredDescriptionDefault
resultNo
coverageNo
data_as_ofNo
coverage_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: phone numbers and home addresses are never collected, contact routes carry provenance (source page, quoted text, personal vs role address), and there is a removal path. It omits error behavior for an unknown id, which keeps it from a 5.

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

Conciseness4/5

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

The core capability is front-loaded in the first sentence, with provenance and privacy notes following in supporting order. It runs a bit long — the removal-request email is arguably tangential to invocation — but no sentence is empty filler.

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?

An output schema exists, so return shapes need not be spelled out, and the description still gives a useful summary of what comes back. Combined with annotation coverage of the safety profile and full parameter documentation, the definition is near-complete; only usage-vs-alternatives guidance is meaningfully absent.

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 the single person_id parameter is already documented, including where to obtain it. The description adds no format or validity detail beyond the schema, so the high-coverage baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — 'Get one investing person by id' — and then enumerates the payload (investing role, roles and firm history, companies, personal investments, contact routes). The 'one ... by id' framing implicitly separates it from the search siblings, but no sibling is named explicitly, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance in the description. It never mentions vc_search_people or vc_get_investor as alternatives, and the only routing hint (where person_id comes from) lives in the schema, not the description.

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.