Skip to main content
Glama

ADITUS Developer Portal MCP

List endpoints of a module

list_endpoints
Read-onlyIdempotent

Every endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.

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": {
      "module": "<module>"
    },
    "name": "list_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
moduleYesModule id, e.g. 'ticket-purchase-registration'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world/non-destructive, so safety is covered. The description adds genuinely new behavioral context by disclosing the projected return fields and noting summaries are truncated to one line — information the agent otherwise could not infer, since there is no output schema.

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?

Two sentences, zero waste, with the returned-field scope front-loaded before the argument-sourcing hint. Nothing restates the name or title verbatim.

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?

For a single-parameter, non-destructive read with no output schema, the description supplies purpose, argument provenance, and return shape. It omits any note on result volume or pagination for modules with many endpoints, which is the one remaining ambiguity.

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?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by tying the 'module' argument to the identifier produced by list_modules, making the required value traceable rather than just typed as a string.

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+resource ('every endpoint of one module') and enumerates the payload it returns (id, method, path, sub-group, summary), which cleanly separates it from the singular get_endpoint and from list_modules.

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?

'Use the module id from list_modules' gives an explicit prerequisite and a concrete path to obtain the required argument. It stops short of naming when to reach for get_endpoint instead, so the exclusion side is only implied by the field list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources