Skip to main content
Glama

Idhall About

idhall_about

Retrieve IDhall platform and REST API version information to verify compatibility and support integration diagnostics.

Instructions

Retourne les informations sur la version d'IDhall et de son API REST.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the disclosure burden, and 'Retourne les informations' plainly signals a non-mutating informational read. For a zero-parameter tool there is little destructive surface left to disclose, though it never explicitly states read-only semantics or any auth requirement. The disclosure is adequate but not stated affirmatively.

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 zero filler, front-loaded with the verb and the two things whose version is reported. Nothing is repeated from the schema and nothing extraneous is included.

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?

An output schema exists, so return values need not be described, and a zero-parameter about tool has minimal complexity to cover. The description covers what is returned (version of IDhall and its REST API) sufficiently. Only marginal context, such as whether it can be used as a connectivity/auth check, is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to add. Baseline for a parameterless tool applies, and the description correctly adds no redundant parameter talk.

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 names a specific verb and resource: it returns version information for IDhall and for its REST API. That is clearly distinct from data-oriented siblings such as idhall_whoami or the idea/endpoint tools. It stops short of explicitly contrasting with a sibling like idhall_api_request, so it is clear but not sibling-differentiating to the top standard.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use statement, nor any named alternative. Usage is strongly implied by the tool's name and zero-parameter shape (a diagnostics/metadata lookup), so an agent can infer the context. No exclusions or routing guidance are given, however.

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