Skip to main content
Glama

Idhall Count Ideas

idhall_count_ideas

Count initiatives that match a specified IdeaFilter to determine how many ideas meet your criteria.

Instructions

Compte le nombre d'initiatives correspondant au filtre donné (IdeaFilter).

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

Input Schema

NameRequiredDescriptionDefault
filterNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

There are no annotations, so the description carries the disclosure burden. 'Compte' clearly implies a read-only, non-mutating operation, but it doesn't explain the default case where filter is null (evidently counting everything), nor any cost or scope implications of an unfiltered count.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is appropriately sized, though the size reflects minimal content rather than maximally useful density.

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 described, which lowers the bar. Still, the sole parameter is completely opaque, and the null/default filter behavior is not addressed, leaving the agent to guess at scope for a count operation.

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 0% and the schema only shows an untyped object or null, so the description effectively adds meaning by naming the expected type ('IdeaFilter'). However, it doesn't enumerate any filter fields or explain what an omitted filter does.

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 concrete verb and resource ('Compte le nombre d'initiatives'), which makes it distinct from list/read siblings like idhall_list_ideas or idhall_get_idea. It lacks an explicit contrast with those siblings, but the count-vs-list distinction is implicit and unambiguous.

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?

It contains no when-to-use or when-not-to-use guidance, and it doesn't point to any alternative. An agent must infer that this is the tool to use for totals rather than enumeration.

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