Skip to main content
Glama

Lovie Company Formation

Plan Network Enrichment

fundraising_plan_network_enrichment
Read-only

Who to enrich next and with which provider: for each person, the first enabled provider in ladder order that their record can feed (LinkedIn, email, phone, or name and company) and that can fill something they lack — skipping providers already tried on them, providers at their weekly cap, never-target people and anyone another enricher holds. 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_plan_network_enrichment"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
picksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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, so safety is covered. The description adds substantial behavior beyond that: ladder-order provider selection, skipping already-tried providers, weekly caps, never-target people, and exclusion of targets held by another enricher — real decision logic not present in structured fields.

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?

It is a single dense sentence that front-loads the core question ('Who to enrich next and with which provider') and then lists exclusion rules. Every clause carries information; the long dash-clause is heavy but not redundant.

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 planning tool with an output schema and clear safety annotations, the description supplies the selection and exclusion logic an agent needs to interpret results. Its one gap is parameter meaning, which the schema only partially covers.

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 only 50%, and the description says nothing about either parameter. The required nested companyId UUID wrapper and the 0–200 limit are left entirely to the schema, with no added meaning about scope or pagination from the description.

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 states a specific purpose — deciding who to enrich next and with which provider per person — beyond the vague title 'Plan Network Enrichment'. It does not name sibling tools like fundraising_claim_network_enrichment or fundraising_get_enrichment_ladder, so an agent cannot route between them from the text alone, keeping it below 5.

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: this is a planning step that produces a target list, likely preceding claim_network_enrichment. However, there is no explicit when-to-use vs when-not guidance and the closely related claim/finish siblings are never mentioned, leaving the agent to infer the sequencing.

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.