Skip to main content
Glama

Edit an investor’s commitment

capital_company_edit_commitment

Use this when the user wants to change an investor’s existing commitment in one of their funds. Starts an edit to the fields they name. Returns Capital Company’s next question, or the proposed edit, with its effect on capital calls already sent, for the user to confirm. This call changes nothing.

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": {
      "request": "<request>",
      "timeZone": "<timeZone>"
    },
    "name": "capital_company_edit_commitment"
  }
}

Input 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

A4.1/5.0
Behavior4/5

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

Adds real context beyond the annotations: the tool stages an edit rather than applying it, returns either Capital Company's next question or the proposed edit with its effect on capital calls already sent, and requires user confirmation. There is mild tension between "This call changes nothing" and readOnlyHint=false, though the two-phase staging explanation largely resolves it rather than contradicting it.

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?

Four short sentences, front-loaded with the usage trigger, then the staging semantics, then the return content, then the safety guarantee. Nothing repeats the schema or the title wastefully.

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?

No output schema exists, yet the description explains what comes back (a follow-up question or a proposed edit plus capital-call impact) and that confirmation is required. For a three-parameter staging tool, an agent has everything needed to call it and interpret the result.

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 coverage is 100%, so team, request, and timeZone are already fully documented in the schema. The description adds only indirect meaning via "the fields they name," implying the freeform request is parsed for target fields, but gives no parameter-level detail beyond that; 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 and resource: changing an investor's *existing* commitment within one of their funds. The word 'existing' implicitly separates it from capital_company_create_commitment, but no sibling is named explicitly, so the differentiation is inferential rather than stated.

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

Usage Guidelines4/5

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

"Use this when the user wants to change an investor's existing commitment" gives a clear triggering condition tied to user intent. It does not state when *not* to use it or explicitly route to create_commitment/update_fund/confirm for adjacent cases, leaving the boundary to inference.

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.

Resources