Skip to main content
Glama

Idhall Add Idea Contribution

idhall_add_idea_contribution

Adds a comment to an initiative, enabling users to capture feedback or sentiment against a specific idea.

Instructions

Ajoute une contribution (commentaire) à 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>",
      "text": "<text>"
    },
    "name": "idhall_add_idea_contribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
idea_idYes
sentimentNo

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, and it discloses almost nothing. It does not say whether the contribution is publicly visible, whether sentiment affects ranking/moderation, whether it requires authorship or membership, or whether duplicate submissions are rejected. Only the core mutation (adds a comment) is conveyed.

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?

A single short, front-loaded sentence with zero padding, which is structurally clean. But given a mutation tool with 0% schema coverage and no annotations, the brevity is under-specification rather than efficiency.

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 explained. Everything else is missing: no parameter meaning, no permission or precondition information, no behavior for the sentiment field, and no differentiation from siblings. For a write operation with no annotations, this leaves the agent materially under-informed.

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% across 3 parameters, so the description must compensate and it does not. "Commentaire" loosely maps to text and "initiative" to idea_id, but the non-obvious optional parameter sentiment (nullable string, default null) is never mentioned — an agent has no way to know what values are meaningful or what its effect is.

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?

States a specific verb and resource: "Ajoute une contribution (commentaire)" — an agent can tell this creates a comment. However, it uses "initiative" where the tool name and all parameters say "idea" (idea_id), introducing terminology drift, and it does not distinguish itself from the read-only sibling idhall_list_idea_contributions. The description is also in French while the tool name, parameters and sibling set are English, which adds avoidable parsing friction.

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 mention of prerequisites (e.g. the idea must exist, be published, or be open to contributions), and no reference to any alternative such as idhall_list_idea_contributions or idhall_create_idea. The agent must infer entirely from the sentence.

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