Skip to main content
Glama
SAP B1 Briefing MCP Server

SAP B1 Briefing MCP Server

check_item_availability

Check stock availability by item code or name, including fuzzy name search, to confirm whether a product is in stock before a customer visit.

Instructions

Check stock/availability for a product by item code or name (supports fuzzy name search).

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": {
      "itemQuery": "<itemQuery>"
    },
    "name": "check_item_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
itemQueryYesItem code or name, as heard/typed (supports fuzzy name search).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden, and it only implies read-only behavior through the verb 'Check'. It says nothing about what is returned (quantity on hand, per-warehouse breakdown, unit of measure), whether out-of-stock items appear, or what a fuzzy miss produces.

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?

A single front-loaded sentence with no filler; the resource and the accepted input forms are stated immediately, and the parenthetical adds a genuinely useful capability note rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no annotations and no output schema, the description should at least sketch the shape of the result or the meaning of 'limit'. Neither is covered, leaving the agent guessing about what availability data comes back.

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 coverage is 50%: itemQuery is already documented in the schema and the description merely restates it, while the 'limit' parameter (default 5, max 20) is undocumented in both places. The description adds no meaning beyond the structured field it echoes.

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 gives a specific verb and resource ('Check stock/availability for a product') plus the lookup keys (item code or name), which is enough to distinguish it from the siblings (business partners, invoices, sales orders). It stops short of explicitly contrasting with any alternative tool, but the purpose is unambiguous.

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: an agent can infer this is the tool for stock questions, and the fuzzy-search note hints at handling imperfect input. There is no statement of when to prefer another tool, no preconditions, and no mention of what to do when nothing matches.

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