Skip to main content
Glama

Idhall Search Endpoints

idhall_search_endpoints

Search the local IDhall v1 endpoint catalog to find the exact endpoint and its endpoint_id before inspecting its schema or making an API request—no network call required.

Instructions

Recherche dans le catalogue local des 208 endpoints IDhall v1 (zéro appel réseau).

Utilisez cet outil pour trouver l'endpoint exact et son endpoint_id avant d'inspecter son schéma avec idhall_get_endpoint_spec ou d'appeler idhall_api_request.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
methodNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the search is local and makes zero network calls, which is important safety/performance context, but it omits matching/ranking semantics and how the default limit or pagination behaves.

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?

The description is short, front-loaded, and every sentence contributes useful context. The local-catalog detail and zero-network-call note are both relevant and not padded with filler.

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?

For a simple search tool with an output schema, the purpose and workflow placement are adequately covered. However, the complete absence of input-parameter semantics leaves a meaningful gap for correct invocation of query, method, and limit.

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

Parameters1/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 for the three undocumented input parameters. It never explains how query is matched, what method filtering does, or how limit constrains results; endpoint_id is only mentioned as a result, not as an input.

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

Purpose5/5

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

States a specific verb and resource: searching the local catalog of 208 IDhall v1 endpoints. It also distinguishes the tool from idhall_get_endpoint_spec and idhall_api_request by framing it as the lookup step before those tools.

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

Usage Guidelines5/5

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

Explicitly says to use this tool to find the exact endpoint and endpoint_id before inspecting its schema or making an API request. It names the relevant alternatives and the workflow condition that selects this search tool.

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