Skip to main content
Glama

Framezone

by app.framezone
OverviewDiscussionsAdmin

Update goal

update_goal
Idempotent

Update a goal: change status, progress, toggle milestones, or add a progress note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoProgress update note (saved in goal timeline)
titleNoNew title
statusNoNew status
goal_idYesGoal ID
priorityNoPriority: 1=high, 2=medium, 3=low
descriptionNoNew description
start_valueNoValue the goal started from; progress is measured from it (use for goals that go down, e.g. 90 -> 80 kg)
target_dateNoNew target date (Y-m-d)
current_valueNoCurrent value (for numeric goals, >= 0)
target_value_numNoTarget value (numeric and habit goals)
toggle_milestoneNoToggle milestone by index (0-based). Ticking the last open one completes the goal; unticking reopens it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / current_value / description
      Previous value: -"Current value (for numeric goals)"New value: +"Current value (for numeric goals, >= 0)"
    • addedInput schema / properties / start_value
      Added value: +{
+  "description": "Value the goal started from; progress is measured from it (use for goals that go down, e.g. 90 -> 80 kg)",
+  "type": "number"
+}
    • addedInput schema / properties / target_value_num
      Added value: +{
+  "description": "Target value (numeric and habit goals)",
+  "type": "number"
+}
    • changedInput schema / properties / toggle_milestone / description
      Previous value: -"Toggle milestone by index (0-based)"New value: +"Toggle milestone by index (0-based). Ticking the last open one completes the goal; unticking reopens it."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the mutation and safety profile is covered. The description adds a list of actions but no deeper behavioral context, such as partial-update semantics or interaction effects between status, progress, and milestone toggling.

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?

A single front-loaded sentence that names the verb, resource, and update categories with zero filler. Every phrase carries information, and the length is appropriate given the schema covers the parameter-level details.

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?

With full schema coverage and annotations covering idempotency and safety, the description is largely sufficient for an 11-parameter update tool. The only notable gap is explicit partial-update semantics—the fact that unprovided fields remain unchanged—which must be inferred from the optional parameters and the update verb.

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 100%, so the schema already documents all 11 parameters. The description's mapping to 'status, progress, toggle milestones, or add a progress note' is helpful at a high level but adds no semantic detail beyond the schema.

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 a goal') and adds a concise list of updateable aspects: status, progress, milestones, and progress note. It is clear enough to be distinguished from create_goal and list_goals, though it does not explicitly name a sibling.

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 phrase 'Update a goal' implies modifying an existing goal rather than creating one, and the listed actions give some context. However, there is no explicit when-to-use versus alternatives guidance, nor any mention of sibling tools like create_goal or complete_task.

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

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