Skip to main content
Glama

Cirra AI Salesforce Admin MCP Server

sf_connection_manage

Destructive

Manage connections to Salesforce orgs associated with the user's Cirra AI account. Call cirra_ai_init at least once before using this tool.

Input Schema

NameRequiredDescriptionDefault
actionYesThe action to perform. Options: 'list' (list all connections), 'describe' (provide details of the connection, including org info and current org limits such as data/file storage, daily API request usage, async job slots, etc.), 'add' (add a new connection), 'reauthenticate' (refresh auth for a connection), 'remove' (remove a connection)
sf_userNo(optional) Salesforce username to identify the connection to use. Omit this to use the current default connection.
cirra_ai_teamNo(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit it when this call carries the context_handle from cirra_ai_init, which names the team for the conversation. A user with more than one place to work (several teams, or a team and a personal account) must pass either the context_handle or 'cirra_ai_team' + 'sf_user'.
context_handleNo(recommended) The conversation context handle returned by cirra_ai_init in this conversation. Pass the exact context_handle value from the most recent cirra_ai_init result so this call runs against the team and Salesforce connection selected for this conversation. A user with more than one place to work (several Cirra AI teams, or a team and a personal account) must pass either this handle or 'cirra_ai_team' + 'sf_user'; a call with neither is refused.

Output Schema

NameRequiredDescriptionDefault
resultNoAction-specific payload: connection details object (describe), array of connection objects (list), array of per-environment authorization URL entries with markdown links (add), a single authorization URL entry (reauthenticate), or the removed connection (remove)
messageYesHuman-readable summary of the result
successYesWhether the operation succeeded
warningNoOptional warning about the current connection or result
instructionsNoFollow-up instructions for the client, e.g. asking the user to open an authorization URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / cirra_ai_team / description
      Previous value: -"(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team."New value: +"(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit it when this call carries the context_handle from cirra_ai_init, which names the team for the conversation. A user with more than one place to work (several teams, or a team and a personal account) must pass either the context_handle or 'cirra_ai_team' + 'sf_user'."
    • addedInput schema / properties / context_handle
      Added value: +{
      +  "description": "(recommended) The conversation context handle returned by cirra_ai_init in this conversation. Pass the exact context_handle value from the most recent cirra_ai_init result so this call runs against the team and Salesforce connection selected for this conversation. A user with more than one place to work (several Cirra AI teams, or a team and a personal account) must pass either this handle or 'cirra_ai_team' + 'sf_user'; a call with neither is refused.",
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "instructions": {
      +      "description": "Follow-up instructions for the client, e.g. asking the user to open an authorization URL",
      +      "type": "string"
      +    },
      +    "message": {
      +      "description": "Human-readable summary of the result",
      +      "type": "string"
      +    },
      +    "result": {
      +      "description": "Action-specific payload: connection details object (describe), array of connection objects (list), array of per-environment authorization URL entries with markdown links (add), a single authorization URL entry (reauthenticate), or the removed connection (remove)"
      +    },
      +    "success": {
      +      "description": "Whether the operation succeeded",
      +      "type": "boolean"
      +    },
      +    "warning": {
      +      "description": "Optional warning about the current connection or result",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / cirra_ai_team
      Added value: +{
      +  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"The action to perform. Options: 'list' (list all connections), 'describe' (provide details of the connection), 'add' (add a new connection), 'reauthenticate' (refresh auth for a connection), 'remove' (remove a connection)"New value: +"The action to perform. Options: 'list' (list all connections), 'describe' (provide details of the connection, including org info and current org limits such as data/file storage, daily API request usage, async job slots, etc.), 'add' (add a new connection), 'reauthenticate' (refresh auth for a connection), 'remove' (remove a connection)"
  4. Added
  5. Removed
  6. Added
  7. Removed
  8. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, so the safety profile is known. The description adds the auth/session prerequisite from cirra_ai_init, which is real value, but it never says that destructive risk is concentrated in the 'remove' action while 'list'/'describe' are harmless reads — an agent could over-apply caution or under-apply it.

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 short, front-loaded sentences with no filler; the prerequisite is easy to spot. It is efficient but so terse that the efficiency shades into under-specification for a five-action tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool tagged destructive with five heterogeneous actions spanning read (list/describe) and mutation (add/remove/reauthenticate), the description says almost nothing about behavior differences. An output schema exists so return values need no explanation, but the action-level behavior gap remains substantial.

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% and the action enum carries per-value semantics, including what 'describe' returns, so the schema does the heavy lifting. The description contributes nothing about action selection, sf_user defaulting, or the context_handle vs cirra_ai_team requirement, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is the vague umbrella "Manage" and the resource is "connections to Salesforce orgs," which is on-target but non-specific. The five distinct capabilities (list, describe, add, remove, reauthenticate) live only in the action enum, so the description itself does not let an agent distinguish scope from siblings like logout or cirra_ai_init.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is a prerequisite: "Call cirra_ai_init at least once before using this tool," which is useful ordering information. There is no when-to-use or when-not guidance per action, and no routing away from siblings such as logout or cirra_ai_init when the intent is ambiguous.

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