Skip to main content
Glama
SAP B1 Briefing MCP Server

SAP B1 Briefing MCP Server

find_business_partner

Search for a customer or vendor by full, partial, or misspelled name and get ranked candidate matches to disambiguate before using a CardCode.

Instructions

Search for a business partner (customer or vendor) by name, even if misspelled or only partially remembered. Returns ranked candidate matches rather than a single forced result — use this to disambiguate before calling other tools with a CardCode.

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": {
      "query": "<query>"
    },
    "name": "find_business_partner"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesThe customer or vendor name as heard/typed, even if misspelled or partial.
cardTypeNoany

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose meaningful behavior: fuzzy matching on names and multi-candidate ranked output instead of a forced single match. It does not state side effects or whether cost/rate limits apply, but "Search"/"Returns" strongly imply a non-mutating read.

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 tight sentences: the first defines the search and its tolerance for bad input, the second defines the return shape and the downstream usage. Nothing is redundant and the key capability is front-loaded.

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 three-parameter lookup with no output schema and no annotations, the description covers the essentials: what is searched, how forgiving the match is, and that multiple ranked candidates come back. The only gap is any hint about result count control or how to narrow by partner type.

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 only 33%, so only `query` is documented in the schema, and the description reinforces its intent (as heard/typed, even if misspelled or partial). The `limit` and `cardType` parameters get no explanation in the description; their meaning is left to schema defaults and the enum values.

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 gives a specific verb and resource ("Search for a business partner (customer or vendor) by name") plus the distinctive tolerance for misspelled or partial input. It also states the return shape ("ranked candidate matches rather than a single forced result"), which separates it from a strict lookup tool.

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

Usage Guidelines4/5

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

It gives explicit usage context: "use this to disambiguate before calling other tools with a CardCode." That tells an agent this is the entry point and must precede CardCode-consuming calls. No when-not guidance or named alternative is given, which keeps it from a 5.

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