Skip to main content
Glama

Dayze — Life Context

Update Goal

update_goal

Patch one owned goal by goal_id from get_goals. Set current_value to absolute progress, not a delta. On a rate goal current_value is this month's number and replaces the last one. Omitted fields remain unchanged. Never select a goal by a guessed ID. request_id required. ($0.10; API key required)

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": {
      "goal_id": "<goal_id>"
    },
    "name": "update_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoProgress note stored with this update, e.g. Finished week 3.
titleNoGoal title, e.g. Run a half marathon.
statusNoGoal status: active, in_progress, completed, paused or abandoned, e.g. completed.
goal_idYesGoal id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
categoryNoGoal category, e.g. health.
priorityNoPriority level: high, medium or low, e.g. medium.
obstaclesNoWhat might get in the way, e.g. Long work travel.
motivationNoWhy the goal matters to the user, e.g. To stay healthy for my kids.
request_idNoClient idempotency key (retries return original result).
descriptionNoWhat the goal is, e.g. Run a half marathon by March.
target_dateNoTarget date YYYY-MM-DD, e.g. 2026-12-31.
target_typeNoGoal type: completion, numeric, rate or habit, e.g. numeric.
target_unitNoUnit for target_value, e.g. km.
target_valueNoNumber the goal aims for, e.g. 21.
current_valueNoAbsolute progress in target_unit, not a delta, e.g. 12.
habit_frequencyNoHow often the habit repeats, e.g. weekly.
idempotency_keyNoAlias for request_id.
checkin_frequencyNoHow often to check in on the goal: daily, weekly or monthly, e.g. weekly.
habit_target_countNoTimes per period needed to hit the habit target, e.g. 3.

Output Schema

NameRequiredDescriptionDefault
goalYes
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
goal_idYes
messageYes
verifiedNo
provenanceNoWhich connector wrote the record and which connected Dayze account received it.
progress_loggedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Goal category, e.g. health."
    • addedInput schema / properties / checkin_frequency / description
      Added value: +"How often to check in on the goal: daily, weekly or monthly, e.g. weekly."
    • addedInput schema / properties / current_value / description
      Added value: +"Absolute progress in target_unit, not a delta, e.g. 12."
    • addedInput schema / properties / description / description
      Added value: +"What the goal is, e.g. Run a half marathon by March."
    • addedInput schema / properties / goal_id / description
      Added value: +"Goal id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809."
    • addedInput schema / properties / habit_frequency / description
      Added value: +"How often the habit repeats, e.g. weekly."
    • addedInput schema / properties / habit_target_count / description
      Added value: +"Times per period needed to hit the habit target, e.g. 3."
    • addedInput schema / properties / motivation / description
      Added value: +"Why the goal matters to the user, e.g. To stay healthy for my kids."
    • addedInput schema / properties / note / description
      Added value: +"Progress note stored with this update, e.g. Finished week 3."
    • addedInput schema / properties / obstacles / description
      Added value: +"What might get in the way, e.g. Long work travel."
    • addedInput schema / properties / priority / description
      Added value: +"Priority level: high, medium or low, e.g. medium."
    • addedInput schema / properties / status / description
      Added value: +"Goal status: active, in_progress, completed, paused or abandoned, e.g. completed."
    • addedInput schema / properties / target_date / description
      Added value: +"Target date YYYY-MM-DD, e.g. 2026-12-31."
    • addedInput schema / properties / target_type / description
      Added value: +"Goal type: completion, numeric, rate or habit, e.g. numeric."
    • addedInput schema / properties / target_unit / description
      Added value: +"Unit for target_value, e.g. km."
    • addedInput schema / properties / target_value / description
      Added value: +"Number the goal aims for, e.g. 21."
    • addedInput schema / properties / title / description
      Added value: +"Goal title, e.g. Run a half marathon."
  2. Changed1 schema field changed
    • changedInput schema / properties / target_type / enum
      Previous value: -[
      -  "completion",
      -  "numeric",
      -  "habit"
      -]New value: +[
      +  "completion",
      +  "numeric",
      +  "rate",
      +  "habit"
      +]
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say it is a non-destructive, non-open-world write; the description adds the semantics that matter: omitted fields remain unchanged, current_value is absolute rather than a delta, and on a rate goal current_value is this month's number replacing the prior one. It also discloses auth and cost ('API key required', '$0.10') and idempotency handling, none of which the annotations convey.

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?

Roughly five short sentences, front-loaded with the identity/scope statement, then the highest-risk semantic trap (absolute vs delta), then the ID-safety rule and cost. Nothing is padded and each sentence carries a distinct constraint.

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 19-parameter mutation with full schema coverage, annotations, and an output schema, the description covers the genuinely dangerous parts: patch semantics, progress semantics for rate goals, idempotency, auth, and cost. It is slightly incomplete in that it declares request_id required while the schema's only required field is goal_id, leaving an agent unsure whether a call without request_id will fail.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the rate-goal interpretation of current_value (this month's figure, replacing the last) and the statement that request_id is required. The absolute-vs-delta rule merely restates the current_value schema text, so it earns no extra credit.

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 first sentence is a precise verb+resource+scope statement: 'Patch one owned goal by goal_id.' Naming get_goals as the ID source and stating that omitted fields are unchanged removes ambiguity about what a patch means here. It does not explicitly contrast with create_goal, but the resource-specific naming already separates it from the update_* siblings.

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?

It gives a real precondition (obtain goal_id from get_goals) and a hard exclusion ('Never select a goal by a guessed ID'), which is stronger guidance than most mutation tools get. It lacks an explicit when-not-to-use case, such as editing a completed or abandoned goal, so it stops short of a 5.

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.