Skip to main content
Glama

Idhall Update Idea

idhall_update_idea

Partially update an existing initiative by sending only the fields you want to change, so records stay accurate without resending the full idea.

Instructions

Modifie partiellement une initiative existante (PATCH /api/v1/ideas/{id}).

Ne passez dans fields que les propriétés à modifier.

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": {
      "idea_id": "<idea_id>",
      "fields": "<fields>"
    },
    "name": "idhall_update_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYes
idea_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does convey that this is a partial PATCH-style mutation rather than a full overwrite. It does not state permissions needed, whether untouched properties are preserved (implied but not stated), validation failures, or anything about the response — an output schema exists, so return values are partly covered, but mutation risk is not.

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?

Two short, front-loaded sentences with no filler; the partial-update rule follows immediately after the identification. The raw endpoint path is somewhat redundant with the tool name but useful as an API anchor.

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 two-parameter partial update, the description covers identity, the route, and the key payload rule, and an output schema covers returns. The one meaningful gap is the shape of the free-form fields object — no list of accepted properties or example — which matters for a nested, unconstrained parameter.

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 coverage is 0% and fields is an untyped free-form object (additionalProperties: true), so the schema provides essentially no meaning. The description partially compensates by explaining that fields should contain only the properties to change, but it never enumerates which properties are valid, leaving the most important ambiguity unresolved.

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 and resource ('Modifie partiellement une initiative existante') and anchors it with the HTTP route PATCH /api/v1/ideas/{id}, so the agent knows exactly which entity is touched. 'Partiellement' distinguishes it from a full replace, but it does not differentiate it from siblings like idhall_create_idea or idhall_transition_idea_stage beyond the obvious create/update split.

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?

It gives one concrete usage rule for the payload ('ne passez dans fields que les propriétés à modifier'), which is real guidance on how to call it. It says nothing about when to prefer this tool over siblings such as transition_idea_stage or manage_idea_tags, nor about prerequisites or required permissions.

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