SAP MCP Server

Get SAP Network Statistics

sap_network_stats

Fetch real SAP network statistics using synapse-sap-sdk DiscoveryRegistry and GlobalRegistry.

SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`detailed`	No	Detailed parameter for Get SAP Network Statistics.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`content`	Yes	MCP content blocks returned to the caller.
`isError`	No	True when the tool result represents an application-level error.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 18, 2026

addedInput schema / additionalProperties
```
Added value: +true
```
removedInput schema / properties / detailed / default
```
Removed value: -false
```

changedInput schema / properties / detailed / description

Previous value: -"Include both discovery overview and raw global registry state."New value: +"Detailed parameter for Get SAP Network Statistics."

Changed1 schema field changedJul 24, 2026

addedInput schema / description

Added value: +"Get SAP Network Statistics input schema. Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. Use exact field names from this schema; do not guess aliases or include private key material."

First observedJul 13, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations show readOnlyHint=false but the description says 'Fetch,' implying a read operation, creating a contradiction. The boilerplate mentions pricing and routing but does not disclose behavioral traits like side effects or required permissions beyond what annotations already provide. Significant gap exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description contains a short opening sentence followed by a large block of repetitive text that repeats the same guidance across four variations. This is verbose and wastes space; every sentence does not earn its place.

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?

While an output schema exists, the description lacks context about what kind of statistics are returned, how the parameter affects results, or any prerequisites. With no behavioral annotations and many siblings, the description is insufficient for an agent to fully understand the tool.

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 coverage is 100%, but the parameter description in the schema is generic ('Detailed parameter for Get SAP Network Statistics'), adding no semantics. The tool description also fails to explain what the 'detailed' parameter does or how its value affects the result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Fetch real SAP network statistics using synapse-sap-sdk DiscoveryRegistry and GlobalRegistry,' which identifies a verb and resource. However, 'SAP network statistics' is vague and not clearly distinguished from many sibling SAP tools like sap_get_network_overview or sap_market_snapshot, making the purpose ambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. A large block of repetitive boilerplate about pricing and routing is generic and does not help differentiate this tool from siblings.

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

All SAP MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.