Skip to main content
Glama

Lovie Company Formation

Update Cap Table Security

cap_table_update_cap_table_security

UpdateCapTableSecurity applies a full update to a holding. Resend every field you mean to keep. vested_pct is computed, never stored: to record shares that were already vested at issuance (a founder's 1,000,000 of 4,000,000, with the other 3,000,000 on a schedule), set vesting.vested_at_issuance_shares and keep the schedule for the rest. Leave vested_pct unset: a non-zero value the holding did not compute in the last 31 days is rejected.

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": {
      "security": "<security>"
    },
    "name": "cap_table_update_cap_table_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
securityYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / security / properties / vesting / properties / vestedAtIssuanceShares
      Added value: +{
      +  "maximum": 10000000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / security / properties / instrumentType / enum
      Previous value: -[
      -  "CAP_TABLE_INSTRUMENT_TYPE_UNSPECIFIED",
      -  "CAP_TABLE_INSTRUMENT_TYPE_SAFE",
      -  "CAP_TABLE_INSTRUMENT_TYPE_COMMON_STOCK",
      -  "CAP_TABLE_INSTRUMENT_TYPE_PREFERRED_STOCK",
      -  "CAP_TABLE_INSTRUMENT_TYPE_OPTION",
      -  "CAP_TABLE_INSTRUMENT_TYPE_CONVERTIBLE_NOTE"
      -]New value: +[
      +  "CAP_TABLE_INSTRUMENT_TYPE_SAFE",
      +  "CAP_TABLE_INSTRUMENT_TYPE_COMMON_STOCK",
      +  "CAP_TABLE_INSTRUMENT_TYPE_PREFERRED_STOCK",
      +  "CAP_TABLE_INSTRUMENT_TYPE_OPTION",
      +  "CAP_TABLE_INSTRUMENT_TYPE_CONVERTIBLE_NOTE"
      +]
    • addedInput schema / properties / security / properties / vesting / properties / fullyVested
      Added value: +{
      +  "type": "boolean"
      +}
    • changedInput schema / properties / security / properties / vesting / properties / totalMonths / minimum
      Previous value: -1New value: +0
  3. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations only declare openWorldHint=false and destructiveHint=false; the description supplies the far more important behavioral fact that this is a full replacement where omitted fields are lost, plus a concrete server-side validation rule (a non-zero vested_pct not computed in the last 31 days is rejected). That is exactly the kind of consequence an agent cannot infer from structured fields. The replace-and-drop behavior sits in mild tension with destructiveHint=false, but it is an update rather than a delete, so this is not a contradiction.

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?

Four sentences, front-loaded with the replace rule before the field-level exception, and every sentence addresses a real failure mode. The founder example (1,000,000 of 4,000,000) is slightly verbose but earns its place by disambiguating a computed field.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the highest-risk trap (vestedPct rejection) is covered well. For a mutation over a very large nested object with no per-field documentation, though, an agent still lacks guidance on which fields are required to be present in a full replace and how untouched-but-omitted fields behave.

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 0% across a ~40-property nested payload, so the description carries real weight — and it does explain two high-risk fields, vestedPct and vesting.vestedAtIssuanceShares, including a worked example and the rule to leave vested_pct unset. It still leaves the vast majority of fields (instrument types, MFN, proRata, strike price, caps, ownership percentages, required companyId/stakeholderId) undocumented, so it only partially compensates.

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 ('applies a full update to a holding') and the critical replace semantics up front, so the agent knows this overwrites rather than patches. It does not name the nearby alternatives (cap_table_update_cap_table_stakeholder, cap_table_get_cap_table_security, cap_table_set_cap_table_pipeline_status), so sibling differentiation is left to the name.

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?

Gives strong operational guidance — 'resend every field you mean to keep' and the vested-at-issuance workflow — which shapes how the call must be made. However it never says when to choose this tool over the sibling update tools (stakeholder update, pipeline status set, round update), so the when-vs-alternative dimension is only implied by 'full update'.

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.