Skip to main content
Glama
sap-s4-mcp

sap-s4-mcp

by Inderj1

list_supplier_invoices

Read-only

Retrieve supplier invoices sorted by posting date, newest first, and filter by supplier ID or posting start date for targeted accounts payable review.

Instructions

List supplier invoices, newest posting date first.

Args: invoicing_party: supplier id to filter on. posted_from: only invoices posted on or after this date (YYYY-MM-DD).

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

Input Schema

NameRequiredDescriptionDefault
topNo
posted_fromNo
invoicing_partyNo

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 sort order, but omits result limits and pagination even though a 'top' parameter with default 20 exists — an agent could easily assume it returns everything.

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?

Front-loaded one-line summary followed by a compact Args block; every sentence carries information. The Args formatting is slightly redundant with the schema but not wasteful.

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 read-only list tool with no output schema and 0% schema coverage, the definition is partially complete: filters and ordering are explained, but the default result cap, pagination behavior, and any indication of returned fields are absent. An agent could call it correctly but not predict the response size.

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 0%, so the description must carry the burden; it documents invoicing_party and posted_from (including the YYYY-MM-DD format), which is real added value. However, the third parameter 'top' is never mentioned despite defaulting to 20, leaving a substantive gap.

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 and resource ("List supplier invoices") and adds the result ordering ("newest posting date first"), which an agent cannot infer from the name alone. It does not explicitly contrast with the sibling list tools (list_proposals, list_sales_orders), but the resource is distinct enough that mis-selection is unlikely.

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 when-to-use guidance, no exclusions, and no mention of alternatives. The only hint of usage is the filter parameters, which imply 'use this to find invoices for a supplier or date range' but state nothing explicit.

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