Skip to main content
Glama

Record an investor’s commitment

capital_company_create_commitment

Use this when the user wants to record that an investor committed to one of their funds. Starts recording the new commitment. Returns Capital Company’s next question, or the proposed commitment for the user to confirm. This call records 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_create_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

A3.7/5.0
Behavior4/5

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

The description adds useful behavioral context beyond the annotations: it explains that the call returns Capital Company’s next question or a proposed commitment for confirmation. It also explicitly says the call records nothing, which is important for understanding the workflow boundary. It could do more to clarify what conversational state, if any, is changed and how this relates to the final confirm step.

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 description is short and front-loads the main usage condition. It is generally efficient, though the sequence 'Starts recording' followed by 'This call records nothing' is slightly tension-producing and could be phrased more cleanly.

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?

For a conversational initiation tool without an output schema, the description covers the intent, the immediate return value, and the fact that no commitment is recorded by this call. It would be stronger if it explicitly routed the agent toward confirm or edit_commitment in adjacent scenarios, but it is otherwise complete enough to invoke 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%, and the schema already documents all three parameters, including the conditional team parameter and the user's own-words request. The description adds no parameter-specific guidance beyond what the schema provides. With full schema coverage, a 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?

The description states a clear verb and resource: recording that an investor committed to a fund. It also clarifies that this is a conversational initiation step returning the next question or a proposed commitment. It does not explicitly distinguish itself from siblings such as edit_commitment or confirm, so it stops short of a 5.

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?

It gives a clear triggering condition: use when the user wants to record that an investor committed to one of their funds. However, it does not say when not to use it or name alternatives like edit_commitment or confirm. The usage context is implied and adequate but incomplete for a crowded sibling set.

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