Skip to main content
Glama

Idhall Get Idea Memo

idhall_get_idea_memo

Retrieves an initiative's memo by idea ID, letting you review stored notes and context for that specific idea.

Instructions

Récupère le mémo d'une initiative.

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

Input Schema

NameRequiredDescriptionDefault
idea_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about permissions, whether a memo can be absent/empty, or whether the call is a pure read. Only the word 'Récupère' weakly implies a non-destructive retrieval.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is structurally clean. But the brevity comes at the cost of under-specification rather than efficiency, and the French wording is not aligned with the otherwise English tool surface.

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?

An output schema exists, so return values need not be described. Still, with no annotations and zero parameter documentation, a one-clause description leaves an agent without enough context to know when this tool is the right choice over its many idea-related siblings.

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 the single parameter (idea_id, integer) is undocumented. The phrase 'd'une initiative' hints that the ID identifies the initiative whose memo is returned, but adds no format, validity, or lookup semantics.

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

Purpose3/5

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

The description gives a specific verb and resource ('Récupère le mémo d'une initiative'), so an agent knows it fetches a memo tied to an initiative. However, it largely restates the tool name and does nothing to distinguish it from close siblings such as idhall_get_idea or idhall_set_idea_memo.

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?

There is no guidance on when to call this versus idhall_get_idea or the other idea-scoped getters, and no stated preconditions (e.g. whether the idea must exist or be published). Usage must be inferred entirely from the name.

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