SAP BusinessObjects MCP Server

Overview Schema Source Related Servers Discussions Admin

refresh_webi_doc

Update a Web Intelligence document by passing its ID and optional prompt answers to refresh report data through SAP BusinessObjects REST services.

Instructions

Refreshes a Web Intelligence document. If the report requires prompts, answers can be passed as a list of objects, e.g. [{"id": 0, "value": "2026"}, {"id": 1, "value": ["Region A", "Region B"]}].

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": {
      "webi_doc_id": "<webi_doc_id>"
    },
    "name": "refresh_webi_doc"
  }
}

Input Schema

Name	Required	Description	Default
`parameters`	No
`webi_doc_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully reveals that prompt answers can be supplied at refresh time, but omits key behaviors for a mutation-style call: whether the refresh persists the document, permission requirements, and whether unprompted documents refresh silently.

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?

Two sentences, front-loaded with the action, and the example earns its length because the schema itself is opaque. Minor slack only in that the example could be tighter.

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?

An output schema exists, so return values need not be described. However, for a mutation tool with zero annotations the description should say more about persistence, permissions, and where prompt IDs come from; as written it covers the action and one input shape but not the full call context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 compensate, and it does well for the opaque `parameters` anyOf array by giving a concrete payload example with both scalar and multi-value entries. `webi_doc_id` and the origin of prompt IDs (get_doc_parameters/get_parameter_lov) remain unexplained.

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 states a specific verb and resource ('Refreshes a Web Intelligence document'), so the operation is unambiguous. It does not, however, distinguish itself from the sibling refresh_dp (data-provider refresh) or clarify scope relative to save_webi_doc, so sibling differentiation is left to inference.

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 explicit when-to-use guidance: nothing says when to refresh a document versus refresh_dp, nor whether the document must be opened/locked first. The conditional prompt case is mentioned, but that is behavioral detail rather than routing guidance.

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