Skip to main content
Glama

Idhall Get Opportunity Analysis

idhall_get_opportunity_analysis

Retrieves the opportunity analysis for a specific initiative by idea ID, helping you assess feasibility, value, and risks before deciding next steps.

Instructions

Récupère l'analyse d'opportunité 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_get_opportunity_analysis"
  }
}

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.4/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 burden of behavioral disclosure. The verb 'Récupère' implies a read, but nothing is said about permissions, whether an analysis may be absent, or what happens for an unanalyzed idea — a significant gap for a tool with zero annotation coverage.

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 definition is a single efficient sentence with no filler, which is fine structurally, but its brevity stems from under-specification rather than disciplined editing. Being a lone sentence also gives no front-loaded context about inputs or behavior.

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, but the tool still has two parameters with 0% schema coverage and no annotations. The description leaves both the 'props' argument and the tool's role relative to sibling analysis/idea tools entirely unaddressed.

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 and it does not: 'idea_id' is only indirectly implied by 'd'une initiative' (and no type or format is given), while the 'props' parameter is completely unaddressed. With two undocumented parameters, the description adds almost no meaning beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The French sentence names a specific verb ('Récupère') and resource ('l'analyse d'opportunité d'une initiative'), so the basic operation is recognizable. However, it offers no differentiation from nearby read tools such as idhall_get_idea or idhall_get_idea_implementation, so an agent cannot tell exactly what distinct payload this returns.

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 indication of prerequisites, and no mention of alternatives among the many idhall_get_* siblings. Usage must be inferred entirely from the resource name.

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