Skip to main content
Glama

Krosos

by com.krosos
OverviewDiscussionsAdmin

record_balance_adjustment

Record a signed quantity change on one holding (a balance update that is not a trade). Same body and validation as POST /api/position-adjustments.

Input Schema

NameRequiredDescriptionDefault
assetYes
tickerYes
accountYes
tx_dateYesToday or tomorrow at the latest (the user's own calendar day); later dates are rejected
tx_timeNoOptional HH:MM on the user's own clock; orders rows within the same day. Omitted: an edit keeps the stored time, a new row takes the current time
providerYes
quantity_deltaYesSigned quantity change (non-zero)
allow_new_valuesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tx_time
      Added value: +{
+  "description": "Optional HH:MM on the user's own clock; orders rows within the same day. Omitted: an edit keeps the stored time, a new row takes the current time",
+  "example": "14:30",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / tx_date / description
      Added value: +"Today or tomorrow at the latest (the user's own calendar day); later dates are rejected"
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states this is a mutation but discloses nothing about permissions, reversibility, rate limits, or what happens to existing values; 'Same body and validation as POST /api/position-adjustments' points to an external API rather than disclosing behavior to the agent.

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?

Two short sentences with the core purpose front-loaded. The endpoint reference sentence is marginally useful but borders on filler.

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?

For an 8-parameter mutation tool with no annotations, no output schema, and incomplete parameter documentation, the description should do substantially more. It leaves behavioral and parameter gaps unaddressed.

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 38%, so the description must compensate and does not. It reinforces the signed/non-zero nature of quantity_delta but leaves asset, ticker, account, provider, and allow_new_values undocumented in both schema and description.

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: 'Record a signed quantity change on one holding,' and clarifies the domain concept ('a balance update that is not a trade'). It partially distinguishes from log_trade but does not name siblings directly.

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?

The parenthetical 'that is not a trade' implies when to use this over log_trade, but there is no explicit when/when-not guidance, no prerequisites, and no named alternatives.

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

All Krosos 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