Skip to main content
Glama
Sign In
SAP Business One Order-to-Cash MCP Server

SAP Business One Order-to-Cash MCP Server

by parmarnaresh86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

switch_company

Switch to a different SAP B1 company database by logging out of the current session and logging into the specified DB to resolve the namespace for subsequent operations.

Instructions

Switch to a different SAP B1 company database. Logs out current session, logs in to new DB, resolves namespace.

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": {
      "dbName": "<dbName>"
    },
    "name": "switch_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbNameYesCompany DB name, e.g. SBO_DEMO_GB

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It explicitly states side effects: logs out current session, logs in to new DB, and resolves namespace. This goes well beyond the tool name, though 'resolves namespace' remains somewhat vague.

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 short sentences front-load the core action and then add the key behavioral details. Every word contributes value, with no repetition or filler.

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?

For a single-parameter tool with no output schema, the description covers all required inputs and the critical session side effects. It could mention what the caller should expect in return or how to verify success, but the operational behavior is sufficiently complete for correct invocation.

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 parameter description in the schema already defines dbName with a clear example. The description adds no additional semantic meaning beyond the schema, so the baseline of 3 applies.

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 a specific verb ('Switch') and a clear resource ('different SAP B1 company database'), which distinguishes it from siblings like get_company_info that merely retrieve information. The first sentence fully states the tool's purpose without ambiguity.

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?

The description implies when to use the tool (when a different company DB is needed), but it does not provide explicit guidance about when not to use it or how it compares to alternatives such as get_company_info. The context is clear, but no exclusions or routing logic are provided.

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