Skip to main content
Glama

Idhall Api Request

idhall_api_request

Send GET, POST, PUT, PATCH, or DELETE requests to any IDhall REST API v1 endpoint, including optional JSON bodies and query parameters.

Instructions

Exécute un appel arbitraire vers n'importe lequel des 208 endpoints de l'API REST IDhall v1.

Avant d'utiliser cet outil sur un endpoint spécialisé (ex: audits, parties prenantes/contacts, ressources/pièces jointes, critères d'opportunité, lots de plan d'action), consultez son schéma avec idhall_search_endpoints et idhall_get_endpoint_spec.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "idhall_api_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesChemin relatif, ex: `/api/v1/stakeholders/12/contacts` ou `risks/1`.
methodYesMéthode HTTP (`GET`, `POST`, `PUT`, `PATCH`, `DELETE`).
json_bodyNoCorps JSON pour `POST`/`PUT`/`PATCH` (ou filtres complexes).
query_paramsNoParamètres de requête (ex: `{"props": ["title", "description"], "page_size": 10}`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 full behavioral burden for what is effectively an unauthenticated-scope HTTP passthrough that supports DELETE and arbitrary JSON bodies. It does add one useful behavior hint — that specialized endpoints have their own specs that should be read first — but says nothing about permissions, whether destructive calls are permitted, rate limits, or failure modes. For a mutation-capable proxy, that leaves a material gap, but the routing caution is genuine added context.

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?

Two sentences, with the core capability front-loaded before the prerequisite. The parenthetical list of endpoint categories is somewhat long, but each item is a genuinely common endpoint family and earns its place by steering the agent to the right spec lookup. Little waste overall.

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 tool spanning 208 endpoints with no output schema, the description correctly focuses on how to discover endpoint-specific contracts. It still omits what a response looks like, how errors surface, and whether auth is implicit — all important for an arbitrary HTTP caller. Adequate but with clear gaps given the tool's complexity.

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 description coverage is 100%, so method, path, json_body, and query_params are already documented in the schema with examples. The description adds no additional parameter meaning, so the baseline of 3 applies rather than anything higher or lower.

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?

States a specific verb and resource: it executes an arbitrary call against any of the 208 IDhall REST API v1 endpoints, which tells an agent exactly what class of operation this is. It also distinguishes itself from the discovery siblings by directing the agent to idhall_search_endpoints and idhall_get_endpoint_spec for specialized endpoints, though it never explicitly contrasts itself with the many dedicated tools such as idhall_create_idea.

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

Usage Guidelines4/5

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

Gives a concrete usage precondition: before hitting a specialized endpoint (audits, contacts, attachments, opportunity criteria, action plan lots), consult its schema via idhall_search_endpoints and idhall_get_endpoint_spec. That is real when-to-use routing to two named alternatives. It stops short of saying when NOT to use this generic proxy in favor of the dedicated per-resource tools, which is the most likely misuse path.

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