mcp-bw-modelling-api

get_infoarea_contents

List all objects within a specific InfoArea in SAP BW. Provide the InfoArea technical name and optionally set a result limit to retrieve its metadata.

Instructions

List all objects within a specific InfoArea.

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": {
      "info_area": "<info_area>"
    },
    "name": "get_infoarea_contents"
  }
}

Input Schema

Name	Required	Description	Default
`info_area`	Yes	Technical name of the InfoArea.
`max_results`	No	Maximum number of results (default: 200).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 24, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'List all objects', but does not mention pagination, the max_results parameter's effect, or any limitations (e.g., whether 'all' is truly all or capped at max_results). Without such detail, the agent cannot anticipate the tool's runtime behavior.

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?

The description is a single, direct sentence with no filler. It front-loads the core action and scope. However, it is almost too terse—slightly more detail on the result set or usage constraints would improve it without harming conciseness.

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, which likely covers return structure, so that gap is mitigated. However, the description does not mention the max_results default or that results may be limited, nor does it hint at any prerequisites (e.g., needing a specific InfoArea technical name). For a listing tool with 2 parameters and no annotations, it is adequate but not comprehensive.

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 100%, so both parameters (info_area and max_results) are fully documented in the schema. The description adds no parameter-specific meaning, but since the schema covers them, the baseline of 3 is appropriate.

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 a clear verb ('List') and resource ('objects within a specific InfoArea'), which conveys the core action. However, it does not explicitly differentiate from sibling tools like list_infoobjects or list_adsos, leaving ambiguity about what 'objects' encompasses and how this differs from related listings.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context where it should be preferred, or situations where a sibling tool would be more appropriate.

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

Deploy Server