Skip to main content
Glama

Capital Company

by ai.capitalcompany
OverviewDiscussionsAdmin

Invite investors to a fund

capital_company_invite_investors

Starts inviting investors to one of the user’s funds by email address. The assistant resolves the fund, asks for what is missing, and puts the invitations to the user for confirmation before any is sent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoThe team to act on, by name, only when the user belongs to more than one team; leave it out otherwise
requestYesWhat the user asked for, in their own words
timeZoneYesThe user’s IANA time zone, such as America/New_York

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / timeZone / description
      Previous value: -"The user’s IANA time zone, such as America/New_York; leave it out when the client reports it with the call"New value: +"The user’s IANA time zone, such as America/New_York"
    • changedInput schema / required
      Previous value: -[
-  "request"
-]New value: +[
+  "request",
+  "timeZone"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this initiates an action rather than a pure read. The description adds valuable behavioral context: the assistant resolves the fund, asks for missing info, and requires user confirmation before sending. This confirms a safe, non-destructive flow with a confirmation gate, going beyond structured annotations.

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?

Two sentences, front-loaded with the core action and then the workflow. No redundancy or filler; every clause earns its place.

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?

The description covers the tool's purpose, the confirmation workflow, and the fact that missing information is requested. With no output schema and annotations covering safety hints, the description is complete enough for an agent to invoke it correctly, though it could clarify what 'resolves the fund' entails.

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 the input schema fully documents all three parameters (team, request, timeZone). The description adds no additional parameter-level detail, so baseline 3 is appropriate.

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+resource: 'inviting investors to one of the user's funds by email address.' Clear what the tool does. However, it doesn't distinguish from siblings like capital_company_send_capital_calls or capital_company_create_commitment, which also involve investor-facing communications.

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?

The description implies usage (when the user wants to invite investors) but doesn't explicitly say when to use this tool vs alternatives like capital_company_send_capital_calls or capital_company_create_commitment. No exclusions or prerequisites are stated.

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

All Capital Company 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