Skip to main content
Glama
Sign In
Salesforce MCP Server

Salesforce MCP Server

by sudhakar6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sf_org_health

Assess Salesforce org health: view org type, current API/storage/async limits, and license seat usage across user, permission set, and installed package licenses.

Instructions

Report the org's overall health: what kind of org it is, current API/ storage/async limits, and license seat usage (user licenses, permission set licenses, installed package licenses).

A heavier, broader report than sf_api_usage (which only checks the daily API request limit) — use this for "what does this org have and how much of it is used", not for a quick mid-conversation limit check.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It signals a read-only report operation and warns that it is 'heavier' and 'broader', implying a potentially costly call. It lists exactly what data will be collected, which is useful for setting agent expectations.

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?

The description is tightly written in two clear parts: what the tool reports, then when to use it versus the sibling. Every sentence adds either content or routing guidance, and the key distinction is front-loaded.

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

Completeness5/5

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

For a no-argument, read-only diagnostic tool, the description fully covers what the agent needs to select and invoke it appropriately. It names the included data categories, warns about cost, and directs the agent away from inappropriate use. No output schema exists, but the description compensates by describing the report scope.

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 has zero parameters, so there is nothing for the description to explain about arguments. Without any invocation parameters, the description's focus on scope and purpose suffices.

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?

The description uses the specific verb 'Report' with the resource 'org's overall health' and enumerates concrete content areas: org type, API/storage/async limits, and license seat usage. It clearly distinguishes itself from sibling sf_api_usage by framing itself as a heavier, broader report.

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

Usage Guidelines5/5

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

Explicit usage guidance is provided: use this for 'what does this org have and how much of it is used' and not for a quick mid-conversation limit check. The alternative sf_api_usage is named and its narrower scope is described.

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