Skip to main content
Glama

Connect Salesforce

connect_salesforce

A link your person opens to approve Bullpen in Salesforce, so every call writes there. Admin or manager only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare non-read-only, open-world, non-destructive; the description adds the meaningful behavior that a human must open the link and approve, and that the result is every call writing to Salesforce. That human-in-the-loop nature is genuinely new context. It stops short of saying what is returned or how long the link lives.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no padding, and the effect (calls write to Salesforce) is front-loaded. But 'A link your person opens' is clumsy and slightly cryptic, costing clarity without saving meaning.

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

Completeness3/5

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

For a zero-param connection tool the description covers who may use it and what enabling it achieves. It omits that the tool returns a URL to be handed to the person, and any expiry/single-use behavior, which an agent needs to relay the link correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies since no parameter semantics are needed.

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 description conveys that this produces a link a user opens to authorize Bullpen in Salesforce, so calls write there, which is enough to identify an OAuth-connect action. However, 'A link your person opens' is awkward phrasing and never states the concrete output (a URL/authorization link) or names the sibling connect_google it parallels. Purpose is inferable rather than stated with a clean verb+resource.

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?

'Admin or manager only' gives a real eligibility constraint that the schema and annotations do not carry. There is no guidance on when to call this versus connect_google, or on whether the link is one-time/expires, so usage context is implied rather than 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.