Skip to main content
Glama
Sign In
Aureon MCP

Aureon MCP

Official
by buildaureon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

aureon_update_objective

Partially update a Financial Compass objective's name, weight, tolerance, priority, risk, and reinvestment ratio. Cannot change target symbol or automation mode; recreate those instead.

Instructions

Partial update (name, weight, tolerance, priority). Cannot change targetSymbol or automationMode — recreate instead.

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": {
      "objectiveId": "<objectiveId>"
    },
    "name": "aureon_update_objective"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
reasonNoOptional note stored on the decision record
priorityNo
toleranceNo
objectiveIdYesObjective ID
maxRiskScoreNo
targetWeightNo
reinvestRatioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.16

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a valuable immutability constraint (identity/automation fields are fixed), but says nothing about permissions/auth, whether omitted fields are left untouched, validation failures, or side effects such as triggering rebalancing or executions.

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?

Two tight clauses with no filler; the mutable-field list is front-loaded and the constraint follows. Every phrase carries information an agent needs.

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 zero annotations, no output schema, and 25% schema coverage, the description is too thin: half the parameters are undocumented in either place, and there is no mention of return behavior or side effects. It covers the immutability rule but leaves the agent under-informed.

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 only 25% (2 of 8), so the description must compensate. It names four mutable fields (name, tolerance, priority, and loosely "weight" for targetWeight) but omits maxRiskScore, reinvestRatio, reason, and objectiveId, and the "weight" naming is ambiguous against the schema's targetWeight.

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+resource ("Partial update" of an objective) and enumerates the mutable fields, which lets an agent distinguish it from aureon_create_objective, aureon_get_objective, and aureon_pause_objective. It is clear without being a tautology, though it does not explicitly name a sibling for contrast.

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?

Provides an explicit when-not and alternative: targetSymbol and automationMode cannot be changed, so the agent should "recreate instead." That is real routing guidance. It stops short of stating prerequisites (e.g. objective must exist, must not be paused) or when to prefer this over other objective-mutating siblings.

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