Skip to main content
Glama

Lovie Company Formation

List Relationships

fundraising_get_list_relationships
Read-only

Lists a company's investor relationships with optional stage, signal, text and connector filters, paginated, plus per-stage counts across the whole pipeline. A count is of relationships in that stage — say so when you report it. 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>"
    },
    "name": "fundraising_get_list_relationships"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNo
pageSizeNo
companyIdYesUUID value wrapper.
pageTokenNo

Output Schema

NameRequiredDescriptionDefault
totalCountNo
stageCountsNo
nextPageTokenNo
relationshipsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces with 'Read-only.' It adds genuine behavioral detail beyond annotations: that it returns per-stage counts across the whole pipeline and that a count reflects relationships in that stage, with an instruction to say so when reporting. It omits pagination mechanics, but the count semantics are a real value-add.

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?

Front-loaded with the core action and scope, followed by a single clarifying caveat about count semantics and a trailing 'Read-only.' Every sentence earns its place with no waste.

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 value shape needn't be explained. The description covers filtering, pagination, and the count behavior, which is sufficient for an agent to call it correctly; only explicit enum/format hints are missing.

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

Parameters4/5

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

With only 25% schema coverage, the description compensates by naming all four filter dimensions — stage, signal, text, connector — which map to the nested filter object's properties, and notes pagination (pageSize/pageToken). It doesn't convey enum values or formats, but it meaningfully explains what each undocumented parameter category does.

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?

States a specific verb (Lists) and resource (a company's investor relationships) plus the dimensions it operates on (filtering, pagination, counts). An agent can distinguish it from fundraising_get_relationship by the plural 'list' scope, though the description does not explicitly name that sibling.

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?

Usage is implied — you use it to enumerate a company's relationships with filters — but there is no explicit when-to-use vs. when-to-use-get_relationship guidance or prerequisites stated. Adequate but leaves selection between list and single-get to the agent.

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.