Skip to main content
Glama

Lovie Company Formation

List Network Merges

fundraising_list_network_merges
Read-only

Recent merges of network people: who survived, which blanks were filled, how many rows moved, and whether the merge was reverted. 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_list_network_merges"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
mergesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' in the description is largely redundant. The description does add the useful semantic that returned records describe merge outcomes (who survived, blanks filled, rows moved, reverted), which is real behavioral context beyond annotations.

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?

A single tight sentence with the subject front-loaded and no filler. The trailing 'Read-only' tag is the only mild redundancy against the annotations.

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?

Output schema exists, so return-value explanation is not required, and annotations cover safety. The description plus structured fields give an agent enough to call it correctly; only the absence of a scoping/recency definition and alternative routing keeps it shy of a 5.

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?

With a single required companyId parameter and 100% schema description coverage, the schema carries the burden. The description adds no information about what the UUID scopes (the network owner company) or any pagination/limit behavior.

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 and resource — listing recent merges of network people — and enumerates the record contents (survivor, filled blanks, row counts, revert status). It distinguishes itself from sibling duplicate-detection tools by being about completed merge history, though it never names an alternative directly.

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 explicit guidance on when to use this versus fundraising_list_network_duplicates, fundraising_scan_network_duplicates, or fundraising_recommend_network_duplicate. Usage is only implied by the word 'Recent' and the 'Read-only' tag.

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.