Skip to main content
Glama

Lovie Company Formation

List Network Events

fundraising_list_network_events
Read-only

Events the founder hosted or attended (Luma, Partiful, calendar, imports) with each guest's RSVP. Only going or checked-in guests were there; an invitation is not a meeting. 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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
eventsNo

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 declare readOnlyHint=true and destructiveHint=false, so 'Read-only' is largely redundant. The description earns credit elsewhere: it discloses the underlying data provenance (Luma, Partiful, calendar, imports) and an important interpretation rule — only going/checked-in guests count as attendance — which is not derivable from any structured field.

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?

Three short sentences, front-loaded with what the tool returns and followed by the interpretive rule. The trailing 'Read-only' is the only sentence that duplicates the annotation block rather than earning its place.

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?

A read-only list tool with one required parameter, an output schema, and full annotation coverage needs little more than this. The description covers source coverage, what a returned guest row means, and the attendance semantics — the gaps (pagination, date filtering) belong to the output schema and absent parameters, not the prose.

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?

Only one parameter (companyId, a nested UUID wrapper) and schema description coverage is 100%, so the schema already does the documentation work. The description adds no meaning about the parameter, which is acceptable at this coverage level but not value-adding.

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?

Names a specific verb+resource (listing network events) and pins down the payload: each guest's RSVP, with sources enumerated (Luma, Partiful, calendar, imports). It implicitly separates itself from the singular sibling fundraising_get_network_event by framing this as a list, but never names that sibling or the Luma-specific connection_list_luma_events alternative.

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?

No explicit when-to-use / when-not-to-use statement and no routing to alternatives such as fundraising_get_network_event or connection_list_luma_events. The clause 'an invitation is not a meeting' does supply a semantic filter rule that shapes how results should be interpreted, which is more than nothing, but it is interpretive guidance rather than tool-selection guidance.

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.