Retrieve current Salesforce user, org ID/name, instance, and API version to establish context before performing other operations.
Current Salesforce user, org id/name/type, instance URL, and API version in use. Call this first to establish context.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint. The description adds concrete payload details (user, org id/name/type, instance URL, API version), which is useful behavioral context beyond the annotations. No contradiction or missing critical traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler: the first states exactly what is returned, the second gives the invocation order. Every phrase earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read-only info tool, the description fully specifies the returned content and the recommended call order. No output schema exists, but the description enumerates the fields, making the tool fully actionable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema description coverage is 100%, so no parameter explanation is needed. Per the baseline for zero parameters, this scores well.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description explicitly enumerates the returned data: current Salesforce user, org id/name/type, instance URL, and API version. This is a specific, distinct purpose and clearly separates get_org_info from the sibling CRUD/query tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly directs the agent to 'Call this first to establish context,' providing a clear when-to-use instruction. It does not name exclusions or alternatives, but no sibling tool overlaps with org-level metadata, so the guidance is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.