Skip to main content
Glama

integrations_set_thread_context

Turn signed thread context on or off for an HTTP-API integration. When on, each call an agent makes to it from inside a conversation carries the conversation's DialogBrain thread id, a timestamp and an HMAC-SHA256 signature made with secret (headers X-DialogBrain-Thread-Id, X-DialogBrain-Timestamp, X-DialogBrain-Context-Signature), so the integration can trust which chat the call comes from. secret (32-128 characters, generated by the integration) is required to turn it on, stored encrypted and never shown back. For a person's own client (API key or MCP) with the admin role; an agent cannot call it.

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>",
      "enabled": "<enabled>"
    },
    "name": "integrations_set_thread_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
secretNoThe HMAC key, 32-128 printable characters, generated by the integration. Required when enabled=true; write-only.
enabledYestrue: sign calls with the thread context. false: stop.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
integration_idYesThe HTTP-API integration's id (from integrations.list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare it is not read-only, so the write framing is consistent. The description adds valuable behavior beyond annotations: the exact headers emitted, HMAC-SHA256 signing with `secret`, that the secret is stored encrypted and never returned, and the caller-authority restriction (admin role, agent cannot call). The only gap is what happens to signatures already in flight when disabled.

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, front-loaded with the action, followed by the mechanics and eligibility. Despite density, every clause carries information an agent needs (what gets sent, key handling, who may call).

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?

Given a mutation tool with no output schema, the description covers effect, credential handling, required inputs and authorization. What the call returns and the idempotence nuance of repeated enable calls are the only omissions.

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 all four parameters are already documented, including the write-only secret and its conditional requirement. The description reinforces that `secret` is needed to turn it on and adds that it is stored encrypted, but it says nothing extra about `in_workspace` or the `enabled=false` path beyond the schema.

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 and resource ('Turn signed thread context on or off for an HTTP-API integration') and scopes it to HTTP-API integrations, which separates it from sibling setters like integrations_set_auth and integrations_set_realtime. An agent can identify the target and effect without opening the schema.

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?

Makes the effect of enabling concrete (each agent call carries thread id, timestamp and HMAC signature) and states a hard prerequisite: a person's own client with the admin role, not an agent. It does not name sibling tools that configure other integration behavior, but the usage context is otherwise explicit.

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.