Skip to main content
Glama

attach_integration_credential

Attaches a vault credential (bearer, API key, or tunnel) to a tenant integration so it can authenticate to a destination. Only one credential per integration; it can't be replaced.

Instructions

Attach a credential from the company's own vault: integration_id, secret_ref (secret name; the platform/ namespace is reserved) and auth_kind (bearer, api_key, tunnel). One credential per integration; it cannot be replaced afterwards

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": {
      "integration_id": "<integration_id>",
      "secret_ref": "<secret_ref>",
      "auth_kind": "<auth_kind>"
    },
    "name": "attach_integration_credential"
  }
}

Input Schema

NameRequiredDescriptionDefault
auth_kindYesAuthentication method for the destination
secret_refYesSecret name in the tenant vault. The platform/ namespace is reserved.
integration_idYesAn integration owned by this tenant

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.4

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a mutation (readOnlyHint=false) and non-idempotent. The description adds important behavior beyond annotations: only one credential per integration and it cannot be replaced afterwards, making the irreversibility clear. It does not cover permissions or success behavior, but adds meaningful operational 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?

A single dense sentence front-loads the action and core parameters, then closes with the critical one-per-integration and non-replaceability constraint. It is efficient, though slightly cramped by packing parameter details and constraints together.

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 simple three-parameter mutation with full schema coverage and no output schema, the description covers the main operational risk (cannot be replaced afterwards) and namespace restriction. It could mention permission requirements or what a successful attach returns, but is largely complete for correct invocation.

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 coverage is 100%, so the schema already documents all three parameters, including the auth_kind enum and the reserved platform/ namespace for secret_ref. The description reinforces these points and mentions the one-credential constraint, but adds little parameter meaning beyond the structured schema.

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: attach a credential to an integration, from the company vault. It identifies the required inputs and key constraints, though it does not explicitly distinguish itself from sibling integration tools such as grant_integration or create_secret.

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?

Implies usage through 'Attach a credential' and the one-per-integration restriction, but gives no explicit when-to-use/when-not guidance or named alternatives. An agent can infer the purpose, but must rely on context for routing decisions.

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