Skip to main content
Glama

Idhall List Idea Contributions

idhall_list_idea_contributions

Lists contributions for a specific initiative using its idea_id, enabling AI clients to review contributor activity and submitted content.

Instructions

Liste les contributions 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_list_idea_contributions"
  }
}

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

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies a read operation. It says nothing about permissions, visibility scope, ordering, or result size, and the only structured relief is the existing output schema covering return shape.

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?

The single sentence is front-loaded and free of waste, but it is concise to the point of under-specification for a two-parameter tool. Brevity here reflects missing content rather than disciplined editing.

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?

The output schema means return values need not be described, but with no annotations, 0% schema coverage on two parameters, and only one vague sentence, the definition is not complete enough for reliable invocation. The undocumented 'props' parameter is the clearest gap.

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%, so the description must compensate, but it only loosely implies that idea_id identifies the 'initiative'. The second parameter 'props' (an optional list of strings) is given no meaning at all in either schema or description, leaving an agent unable to use it deliberately.

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 gives a specific verb and resource ('Liste les contributions d'une initiative'), which separates it from mutation siblings such as idhall_add_idea_contribution and from other list tools like idhall_list_ideas or idhall_list_users. It is slightly weakened by calling the parent object an 'initiative' while the schema parameter is 'idea_id', leaving a small naming ambiguity.

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 when-to-use guidance, no prerequisite statement (e.g. that the idea must exist or be visible), and no mention of any alternative tool. The agent must infer the context entirely from the verb 'Liste'.

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