Skip to main content
Glama
Sign In
monarch-mcp2-obot

monarch-mcp2-obot

by dcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Investments Update Manual Holding

investments_update_manual_holding

Update a manual investment holding by adjusting quantity, cost basis, or security type, ensuring Monarch records reflect current data.

Instructions

Update manual holding. This may create or update Monarch data.

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": {
      "holding_id": "<holding_id>"
    },
    "name": "investments_update_manual_holding"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
quantityNo
cost_basisNo
holding_idYes
output_modeNoOutput shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.summary
security_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish that this is a mutating, non-read-only, non-idempotent operation. The description adds the detail that it 'may create or update Monarch data', which hints at an upsert-like side effect. However, it does not explain what other side effects, permissions, or data changes could occur, so the added transparency is limited.

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-loaded, with no redundant filler beyond the second sentence. It could earn its place more fully, but as a conciseness matter it is efficient.

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

Completeness2/5

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

With six parameters, no output schema, and a mutation operation, this description is far from complete. It does not state which fields are updatable, how the output changes across output_mode values, or how update relates to the create/delete siblings, so an agent would lack critical call context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, and the tool description does not compensate by explaining the key parameters. Quantity, cost_basis, and security_type remain semantically ambiguous (e.g., total cost basis vs. per-share, units, allowed security types), and holding_id is only identified as required, not explained.

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 specific verb and resource, 'Update manual holding', which makes the core operation clear. It is distinguishable from sibling tools like investments_create_manual_holding and investments_delete_manual_holding, though it mostly restates the tool name and adds little beyond that.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus creating, deleting, or retrieving a manual holding. The phrase 'may create or update' hints at upsert behavior but does not explain when that occurs, nor does it mention prerequisites or alternatives.

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

Deploy Server

Other Tools