Skip to main content
Glama

Capital Company

by ai.capitalcompany
OverviewDiscussionsAdmin

Send capital call notices

capital_company_send_capital_calls

Starts sending capital call notices to the investors of a fund class. The assistant resolves the class and its commitments and puts the notices to the user for confirmation before any is sent. It never moves money.

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds meaningful behavioral context beyond them: the assistant resolves the class and its commitments and presents notices for user confirmation before anything is sent, and it never moves money. This goes beyond the structured fields, though the send/confirmation mechanics could be spelled out further.

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 the action and followed by the confirmation and no-money guarantees. No filler, though the description is not maximally tight.

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?

Annotations cover the safety profile and no output schema is needed since the description explains the flow ends in user confirmation. For a non-destructive send tool, the description covers purpose, resolution behavior, and the confirmation gate adequately; minor gaps remain around return/next-step details.

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 all three parameters are already documented in the schema. The description adds no parameter-level detail (e.g., format of request or team handling), so the baseline of 3 applies.

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: 'Starts sending capital call notices to the investors of a fund class.' An agent can identify the action without opening the schema. However, it does not explicitly differentiate itself from the sibling capital_company_send_subscription_agreements, which is a closely analogous send operation.

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 by the resource scope ('investors of a fund class') rather than stated as when-to-use guidance. No explicit when-not conditions or named alternatives are given, so the agent must infer that this is the tool for capital calls specifically vs subscription agreements.

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