Skip to main content
Glama

Idhall Set Idea Memo

idhall_set_idea_memo

Sets or replaces the memo for a specific initiative using its idea ID, keeping the initiative's memo content current.

Instructions

Définit ou remplace le mémo d'une initiative (PUT /api/v1/ideas/{id}/memo).

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>",
      "memo": "<memo>"
    },
    "name": "idhall_set_idea_memo"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoYes
idea_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 behavioral burden. It does disclose the key mutating trait — the existing memo is replaced ("remplace") — and pins the underlying operation via `PUT /api/v1/ideas/{id}/memo`. It says nothing about permissions, error behavior when the idea does not exist, or whether replacement is destructive and irreversible.

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 front-loaded sentence with the action first and the endpoint in parentheses. Nothing is wasted, though the endpoint reference is marginally redundant with the tool's own behavior statement.

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

Completeness3/5

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

For a two-parameter mutation with an output schema (so return values need no explanation), the minimum is met: what it does, which idea, what field. Missing are the prerequisite that the idea must exist, whether the memo is fully overwritten or merged, and any permission requirement — all things an agent would otherwise have to discover by trial.

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 0% and both parameters are required, so the description must compensate. The endpoint template shows `{id}` maps to the path (idea_id) and implies memo is the request body payload, but it never says what a memo is — free text, markdown, length limits — nor what happens on empty or oversized input.

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 pair ("Définit ou remplace") and a specific resource ("le mémo d'une initiative"), so an agent can distinguish it from the read counterpart idhall_get_idea_memo. It stops short of explicitly naming that sibling or any other alternative, which keeps it out of 5 territory.

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?

"Définit ou remplace" implies upsert semantics — call this whether or not a memo already exists — which is genuinely useful guidance for choosing it over a hypothetical create-only tool. There is no explicit statement of when not to use it, no prerequisite (e.g. the idea must exist), and no mention of alternatives such as updating the idea through idhall_update_idea.

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