Skip to main content
Glama

Lovie Company Formation

Get Network Person

fundraising_get_network_person
Read-only

One network person with their roles at companies and firms, the groups and events they were met in, and the investor relationships that name them. A merged person resolves to whoever absorbed them. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
personIdYesUUID value wrapper.
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
personNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds useful behavioral context that merged people resolve to the absorbing record, which is not available from annotations, but it does not describe permission requirements or error behavior.

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 front-loaded with the resource and return composition, then adds merge behavior and read-only status in compact form. It is appropriately sized for the tool with no wasted exposition.

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?

With annotations covering safety and an output schema covering return shape, the description is largely complete for a single-resource getter. It still leaves the required company/person identifier semantics to the schema, which is acceptable here but not fully explanatory.

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%, so the two required UUID parameters are structurally documented. The description adds no semantics about how companyId scopes the lookup or how personId interacts with merged-person resolution, leaving parameter meaning at the schema baseline.

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 clearly identifies a single network person and enumerates the related data returned: roles, groups, events, and investor relationships. It implicitly distinguishes itself from list_network_people by saying "One network person," though it does not explicitly name sibling tools.

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

Usage Guidelines3/5

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

The phrase "One network person" implies this is for retrieving details on a known individual rather than listing people, and "Read-only" signals safe retrieval. However, it gives no explicit when-to-use guidance, exclusions, or named alternatives such as list_network_people or get_network_graph.

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.