Skip to main content
Glama
sap-s4-mcp

sap-s4-mcp

by Inderj1

list_proposals

Read-only

Retrieve SAP S/4HANA write proposals and filter by status (pending, executed, rejected, failed) to review changes awaiting approval.

Instructions

List write proposals and their status (pending, executed, rejected, failed).

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_proposals"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNopending

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 structurally. The description adds the set of possible proposal states, which is genuinely useful context, but says nothing about default filtering, result volume, or ordering — relevant given openWorldHint=true.

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?

A single short sentence with the resource and the state vocabulary front-loaded; nothing is padded. It could add one clause about filtering without becoming verbose.

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 one-optional-parameter read tool with no output schema, this is close to adequate, but the default-pending behavior and whether results are filtered or exhaustive are left unexplained. The status enumeration partly compensates and keeps it at minimum viable.

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 parameter meaning. The enumeration "pending, executed, rejected, failed" does effectively document the accepted values of the status parameter, but it never states that the parameter is a filter or that omitting it defaults to pending.

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+resource ("List write proposals") and enumerates the status values returned, which is enough to distinguish it from read-oriented siblings like list_sales_orders. It stops short of explicitly naming a contrasting sibling, 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 Guidelines2/5

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

There is no guidance on when to call this versus alternatives, no mention that results are filtered by the status parameter, and no note about what happens when status is omitted (schema default is "pending"). The agent must infer the filtering behavior entirely.

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