Skip to main content
Glama

Idhall List Ideas

idhall_list_ideas

List IDhall initiatives with pagination, property projection, structured filters, and optional total counts to build focused, paged result views.

Instructions

Liste les initiatives IDhall avec pagination, projection (props) et filtres (filter).

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

Input Schema

NameRequiredDescriptionDefault
countNoSi True, inclut le nombre total de résultats.
propsNoPropriétés à inclure (ex: ["title", "description", "plan", "stage", "author"]).
filterNoFiltre structuré conforme à `IdeaFilter` (ex: {"plan": 1, "title": "Qualité"}).
offsetNoIndex de départ (>= 0).
page_sizeNoNombre d'éléments par page (1 à 100, défaut 20).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the behavioral burden. It mentions pagination, projection and filtering, but does not disclose read-only/safety behavior, authentication needs, rate limits, or other side-effect context.

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?

It is a single front-loaded sentence with no filler, and every clause adds purpose or capability information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-optional-parameter list tool with a fully described input schema and an output schema, the description plus schema is sufficient to invoke the tool correctly. It still lacks sibling-routing guidance, so it is not fully complete.

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 coverage is 100%, so count, props, filter, offset and page_size are already fully documented in the input schema. The description only names props and filter at a high level, which meets the baseline when schema does the heavy lifting.

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, "Liste", and resource, "initiatives IDhall", plus the supported capabilities of pagination, projection and filtering. It does not explicitly distinguish itself from sibling idhall_count_ideas, so it is clear but not fully sibling-differentiated.

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 or when-not-to-use guidance, and it does not say to prefer idhall_get_idea for a single item or idhall_count_ideas for totals. Usage is only implied by the verb "Liste".

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