Skip to main content
Glama
sap-s4-mcp

sap-s4-mcp

by Inderj1

search_business_partners

Read-only

Find customers or suppliers by partial name and return their ID, full name, category, and creation date for business partner lookup.

Instructions

Find business partners (customers, suppliers) by part of their name.

Returns id, full name, category (1 = person, 2 = organization) and creation date.

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

Input Schema

NameRequiredDescriptionDefault
topNo
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 usefully adds the returned fields and the category encoding (1 = person, 2 = organization). It says nothing about result limits or ordering even though a 'top' default of 20 exists, so behavioral disclosure is partial.

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?

Two sentences, front-loaded with the action and scope, and the second sentence earns its place by documenting return values in the absence of an output schema. Slightly more compact phrasing could have folded the return list into one line, but there is little waste.

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?

With no output schema, the explicit return fields are valuable and largely close that gap. However, for a two-parameter search tool with 0% schema coverage, missing details on the 'top' limit, ordering, and the fact that the empty-string default presumably matches broadly leave real holes.

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%, so the description carries the full burden, and it only clarifies one parameter loosely ('by part of their name' implies substring matching for name_contains). The 'top' parameter is never explained in the description or the schema beyond its title and default of 20, leaving its limit semantics undefined.

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?

The description states a specific verb and resource — find business partners — plus the search key ('by part of their name') and the entity subtypes (customers, suppliers). This implicitly separates it from sibling get_business_partner, which appears to be an ID-based lookup, though no sibling is named explicitly.

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?

Usage is only implied: the phrase 'by part of their name' tells an agent this is a partial-name search rather than an exact fetch. There is no statement of when to prefer this over get_business_partner, no prerequisites, and no note on behavior when the search term is empty.

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