Skip to main content
Glama
Sign In
AIOProductOS

AIOProductOS

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
JavaScript
Remote

Update Objective

update_objective
Idempotent

Update an objective's name, description, or period. Omitted fields stay unchanged; null clears description or period.

Instructions

Update an objective's name / description / period and return it; omitted fields are unchanged (null clears description or period). Resolve the id via list_objectives; only id is required. To move a key result's value use update_key_result.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "obj_123",
      "name": "Reach $75k MRR"
    },
    "name": "update_objective"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesObjective id, from list_objectives (required).
nameNoNew name (optional).
periodNoNew period, e.g. 'Q4 2026'; null clears it (optional).
descriptionNoNew description; null clears it (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.14
  2. Removedv0.1.12
  3. Addedv0.1.6

TDQS

A4.7/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond annotations: partial update semantics ('omitted fields are unchanged'), null clearing behavior, and that the tool returns the updated objective. Annotations already cover idempotency and non-destructiveness, so this is a strong supplement.

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 sentences: the first states the core behavior and edge-case semantics; the second gives prerequisite and alternative. No filler, front-loaded, and every sentence earns its place.

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

Completeness5/5

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

For a simple update tool with 4 well-documented params and no output schema, the description covers the essential context: what updates, what happens when fields are omitted/null, how to resolve the id, and a sibling alternative. Nothing crucial is missing.

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 the baseline is 3. The description adds value by explaining the overall update semantics and specifically noting how to obtain the id ('Resolve the id via list_objectives'), which is not in the schema. Null semantics are already in the schema but reinforced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is specific: it names the resource ('objective') and the exact updatable fields ('name / description / period'). It also distinguishes from siblings by pointing to update_key_result for key result value moves and implicitly contrasts with create_objective.

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

Usage Guidelines5/5

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

The description provides clear usage guidance: how to resolve the id via list_objectives, that only id is required, and an explicit alternative tool (update_key_result) for a different use case. This goes beyond generic guidance.

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