Skip to main content
Glama

Idhall List Reference Items

idhall_list_reference_items

Lists IDhall reference catalog items such as plans, sites, organizations, categories, risks, and stakeholders, with filtering, field selection, and pagination to support IDhall data workflows.

Instructions

Liste les éléments d'un référentiel IDhall (plans, sites, organizations, categories, risks, stakeholders, etc.).

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": {
      "resource": "<resource>"
    },
    "name": "idhall_list_reference_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
propsNo
filterNo
offsetNo
resourceYes
page_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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, yet it only says the tool "lists." It does not state that the operation is read-only, how pagination defaults behave (page_size 50, offset 0), what ordering is applied, or whether filters combine. It also switches to French while the schema and sibling names are English, adding avoidable friction.

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 or repetition. It is efficient, though the brevity is partly under-specification rather than disciplined concision.

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 shape need not be explained, but for a 6-parameter, enum-driven listing tool with zero annotation coverage the description is too thin. Filtering syntax, prop selection, count mode, and pagination behavior are all left undocumented, which is a material gap for correct invocation.

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 6 parameters, and the description compensates only for `resource`, and only by giving example values rather than explaining the enum semantics (e.g., what 'risk-types' versus 'risks' returns). The `filter`, `props`, `count`, `offset`, and `page_size` parameters receive no explanation at all, leaving prop projection and count-vs-list behavior undefined.

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 ("Liste") and resource ("les éléments d'un référentiel IDhall") and enumerates example resource types (plans, sites, organizations, categories, risks, stakeholders). This makes the tool's role as a generic reference-data lister clear. It stops short of explicitly contrasting itself with the siblings that list domain objects (ideas, users), so a 4 rather than a 5.

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 guidance on when to use this tool versus alternatives, no prerequisite or permission notes, and no indication of when to page through results. The only implied usage is "you want to see reference data," which an agent must infer from the resource examples.

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