Skip to main content
Glama

Idhall Get Idea

idhall_get_idea

Retrieve an initiative's details by its ID; pass props to return fields beyond the default id and title.

Instructions

Récupère les détails d'une initiative par son ID. Passez props pour obtenir plus que {id, title}.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
propsNo
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?

No annotations exist, so the description carries the full behavioral burden. It does disclose one genuinely useful trait beyond the schema: the default response is truncated to {id, title} and `props` widens it. It says nothing about permissions, behavior for a nonexistent ID, or whether additional sub-resources must be fetched separately.

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 short sentences with no wasted wording; the core action comes first and the payload-expansion tip follows. Front-loading is correct and nothing is redundant.

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?

With an output schema present, the return shape is partly covered, and the description's default-payload note fills an important gap. Still, for a getter whose only optional parameter is a free-form property-name array, the absence of any guidance on what names `props` accepts leaves the agent guessing when expanding the response.

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 description coverage is 0%, and the description does add meaning for both parameters: `idea_id` identifies the initiative, and `props` selects which fields beyond {id, title} are returned. However, `props` is an untyped-at-runtime string array with no enum, and the description never hints at valid property names or accepted values, which is the single most important semantic gap.

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 ('Récupère les détails d'une initiative par son ID'), so it is clearly a single-item getter keyed by ID. It is distinguishable from the sub-resource siblings (idhall_get_idea_memo, _tags, _stage) by implication, but it never explicitly says it returns the base object rather than those sub-resources.

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?

Usage is only implied: the second sentence tells the agent that omitting `props` yields a minimal payload, which nudges toward passing `props` when details are needed. There is no explicit when-to-use/when-not guidance and no pointer to the sibling sub-resource tools for memo, tags, or stage.

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