Skip to main content
Glama
sap-s4-mcp

sap-s4-mcp

by Inderj1

get_business_partner

Read-only

Retrieve a single SAP S/4HANA business partner and its addresses by ID to verify customer or supplier details before sales or invoice actions.

Instructions

Get one business partner with its addresses.

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": {
      "business_partner": "<business_partner>"
    },
    "name": "get_business_partner"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_partnerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that addresses are returned alongside the partner, which is useful payload context. It does not say how a missing partner is reported or what identifier form is expected, which matters for an open-world lookup.

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?

One short sentence with the resource and the return scope front-loaded and no filler. It is arguably too terse, but nothing in it is wasted.

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 single-parameter read with annotations covering safety and no output schema, the description is close to sufficient. The remaining hole is the identifier semantics of the one required argument, which neither schema nor description resolves.

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

Parameters2/5

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

Schema description coverage is 0% for the single required 'business_partner' parameter, so the schema supplies only a title. The description does not clarify whether the value is an internal ID, a number, or a name, leaving the identifier format entirely to guesswork on a required field.

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

Purpose4/5

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

States a specific verb (get) and resource (business partner) with singular scope ('one'), which implicitly separates it from the sibling search_business_partners. It also notes the response includes addresses, so the agent knows this is a detail-fetching read.

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?

There is no explicit when-to-use guidance, no statement of when to prefer search_business_partners, and no note about prerequisites or what happens if the partner doesn't exist. The singular 'one' is the only implicit usage signal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.