Skip to main content
Glama

Modifier un objectif

dandori_update_goal
Idempotent

Modifier un objectif existant ; seuls les champs fournis changent.

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": {
      "id": "<id>"
    },
    "name": "dandori_update_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID de l'objectif
tagsNoNoms des tags à associer (créés automatiquement s'ils n'existent pas)
titleNo
periodNo
statusNo
end_dateNoDate de fin / cible (YYYY-MM-DD)
space_idNoChanger d'espace
start_dateNoDate de début (YYYY-MM-DD)
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false and openWorld=false, so the safety profile is carried by structured data. The description's one contribution beyond that is the PATCH-style semantics that omitted fields are preserved, which is genuinely useful for avoiding accidental overwrites, but it says nothing about side effects such as tag auto-creation or the consequences of moving a goal to another space via space_id.

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?

A single short sentence with zero waste, and the partial-update rule is front-loaded where an agent will see it. It is arguably too terse for a 9-parameter mutation, but that shortfall is captured under completeness rather than verbosity.

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 a 9-parameter mutation with no output schema and only 56% schema coverage, the description is significantly under-specified. It omits permissions required, validation constraints on dates and enums, tag replacement semantics, space-change side effects, and what the tool returns after a successful update.

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 56% across 9 parameters, so the description needs to compensate and it does not. It adds no meaning for title, status, period, description, or the date fields, and says nothing about whether tags replace or append to existing tags, which is the highest-risk ambiguity in 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 names a specific verb (modifier) and resource (objectif) and adds real semantic content: the update is partial, since only supplied fields change. It does not explicitly distinguish itself from dandori_create_goal or the other dandori_update_* siblings, but the name-plus-description combination leaves no ambiguity about what the tool does.

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

Usage Guidelines2/5

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

The only usage cue is 'existant', which implies the goal must already exist. There is no guidance on when to prefer this over dandori_create_goal, no prerequisite or permission information, and no statement about whether completed or archived goals can be modified.

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.

Resources