Skip to main content
Glama

integrations_get_endpoints

Read-onlyIdempotent

List every endpoint (operationId, method, path, and description when it has one) registered on an HTTP-API integration. Identify it by integration_id or base_url. Use this to review what tools exist before integrations.remove_endpoints or add_endpoints.

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": "integrations_get_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_urlNoOr the integration's base URL, e.g. https://api.boomnow.com
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
integration_idNoIntegration id (from integrations.list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world, non-destructive call, so the safety profile is covered. The description adds value by disclosing the shape of what comes back (operationId, method, path, optional description) and that the integration can be addressed two ways. It does not cover pagination, large-integration behavior, or what happens if the integration cannot be resolved.

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?

Three short sentences with the resource, the return payload, the addressing options, and the routing advice in that order. Nothing is padded and the most decision-relevant content (what it returns, when to use it) is front-loaded.

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 read-only listing tool with an empty required-parameter list and no output schema, the description does the heavy lifting by describing the return fields and the two addressing modes. The one remaining gap is that all three parameters are optional, so behavior when neither integration_id nor base_url is supplied is not stated.

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 the schema already documents all three parameters, including the "Or the integration's base URL" alternative for base_url. The description restates the integration_id/base_url either-or choice, which is mildly useful but largely duplicative of structured data; baseline 3 applies.

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?

The description names a specific verb and resource ("List every endpoint ... registered on an HTTP-API integration") and enumerates the returned fields (operationId, method, path, description). It also distinguishes itself from the mutation siblings integrations.remove_endpoints and integrations_add_endpoints, so an agent can pick it without opening another schema.

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?

It states the use case explicitly ("review what tools exist") and positions it relative to two named alternatives, add_endpoints and remove_endpoints, which are the operations whose correctness depends on knowing existing endpoints. No inference about when to reach for it is required.

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.