Skip to main content
Glama
Sign In

fundz

by net.fundz
OverviewDiscussionsAdmin

Get Engage network opportunities

get_engage_opportunities
Read-onlyIdempotent

Engage opportunities: recent LinkedIn posts by people in the user's OWN network (or at their target accounts) about a company with a fresh Fundz event, each with why it matched, the post link, a suggested DM and comment in the user's voice, and its status (delivered, contacted, replied, booked). Same list as app.fundz.net/engage. Needs Engage set up (LinkedIn connections uploaded). Use with get_daily_leads (icp: "all") for one deduplicated account list across every ICP plus warm network paths. Never send a DM or comment for the user; show the draft and let them post it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_engage_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow far back, in days (default 14, max 90).
limitNoMax opportunities (default 20).
statusNo"open" (default) = not yet contacted or dismissed; "all" includes contacted, replied, booked and dismissed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the tool never sends DMs or comments and only surfaces drafts for the user to post — an important safety constraint that reinforces the annotations rather than contradicting them. It also pins the data source to the same list as app.fundz.net/engage and defines the status lifecycle values, though it says nothing about ordering, pagination, or empty-result behavior.

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 resource definition is front-loaded and each of the three sentences carries distinct information: what an opportunity is, the setup prerequisite plus sibling pairing, and the no-autosend rule. The opening sentence is dense and long but not padded; nothing reads as filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully carries the return-shape burden by listing the fields each opportunity contains and the status values. Combined with the stated setup prerequisite and the read-only, draft-only behavior, an agent has everything needed to call and interpret it correctly.

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 days, limit, and status are already fully documented with defaults and bounds, establishing the baseline of 3. The description's mention of status values (delivered, contacted, replied, booked) loosely maps to the status enum but adds no syntax or interaction detail beyond the schema.

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

Purpose5/5

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

The description names a specific verb and resource (Engage opportunities = recent LinkedIn posts by people in the user's network) and enumerates the exact payload of each item (why it matched, post link, suggested DM/comment, status). It distinguishes itself from siblings by naming get_daily_leads and explaining the relationship, so an agent can identify it without opening the schema.

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

Usage Guidelines5/5

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

It states the prerequisite explicitly (Engage must be set up with LinkedIn connections uploaded) and gives a concrete complementary pattern: pair with get_daily_leads (icp: "all") to build one deduplicated account list plus warm network paths. That is both a when-to-use condition and a named alternative workflow rather than an implied one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All fundz toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources