Skip to main content
Glama

create_integration

Register a tunnel, API, or MCP integration with a name, target, sharing setting, and access limits; create a new one to change immutable target or limits.

Instructions

Register an integration: kind (tunnel, api, mcp), name, target, shareable, limits. target and limits are immutable — to change them, create another integration

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": {
      "kind": "<kind>",
      "name": "<name>"
    },
    "name": "create_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesHow the destination is reached
nameYesHuman-readable resource label
limitsNoAccess limits; immutable after creation. Create a new integration to expand its scope.
targetNoDestination descriptor, such as tunnel origin/path, base_url or server reference. Immutable after creation.
shareableNoWhether the integration can be shared; defaults to false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the write/non-idempotent profile is covered structurally. The description adds the important constraint that `target` and `limits` are immutable, but that is largely restated from the schema property descriptions, and it says nothing about auth requirements, duplicate-name behavior, or what is returned on creation.

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 tight sentences with the core action and the key constraint front-loaded; nothing is wasted. The backtick-heavy enumeration is slightly list-like but efficient.

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 tool with nested `target`/`limits` objects and no output schema, the immutability warning covers the main non-obvious risk. Remaining gaps (return value/identifier, relationship to credential attachment) are modest and partly mitigated by full schema coverage.

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 baseline is 3; the description mainly echoes parameter names and the `kind` enum already present in the schema. The immutability note for `target` and `limits` duplicates what the schema properties already say, adding no new format or shape detail for the nested objects.

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 ('Register an integration') and enumerates the five fields involved, including the enum values for `kind`. It is clearly a creation tool, distinguishable from sibling operations like attach_integration_credential or grant_integration, though it never names or routes against those siblings.

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?

Usage is implied by 'Register' and the immutability clause implies a when-not for modification ('to change them, create another integration'), but there is no explicit guidance on prerequisites (e.g. credentials must be attached afterwards) or on choosing between `tunnel`, `api`, and `mcp` kinds.

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

Deploy Server

Other Tools