Skip to main content
Glama

Idhall Get Idea Input Availability

idhall_get_idea_input_availability

Retrieve available and required fields for creating or modifying an initiative, with optional idea_id and plan_id parameters to guide the correct input set.

Instructions

Retourne les propriétés disponibles/requises pour créer (idea_id=None) ou modifier une initiative.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "idhall_get_idea_input_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
idea_idNo
plan_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It implicitly signals a read-only introspection via 'Retourne' and 'disponibles/requises', and discloses the two operating modes via the idea_id=None condition — useful context beyond the schema. However, it says nothing about the shape of the result, error cases, or permissions, and completely omits plan_id's role.

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?

A single sentence with the operating condition front-loaded inside the parenthetical, and no filler. Every clause contributes to the meaning.

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?

An output schema exists, so return values need not be spelled out, and the create-vs-modify distinction is captured. Against that, plan_id is entirely unexplained and the description never states that this is a read-only discovery call meant to precede a create/update. For a two-parameter introspection tool this is adequate but has a clear hole.

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%, so the description must compensate for both parameters. It handles idea_id well by defining the null value as create-mode and a set value as modify-mode, which is exactly the semantics the schema lacks. plan_id is never mentioned, leaving half the parameters undocumented in both schema and description.

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 states a specific verb and resource: it returns the available/required properties for creating or modifying an idea. That is clearly a schema-introspection tool rather than a mutator, which distinguishes it from siblings like idhall_create_idea and idhall_update_idea. It does not name those siblings, and the switch between 'idée' (implied by idea_id) and 'initiative' introduces mild terminology drift.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete, parameter-driven when-to-use rule: call it with idea_id=None to discover input properties for creation, and with an idea_id to discover properties for modification. There are no explicit exclusions or named alternatives, so the agent must infer that this should precede create/update calls.

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