mcp-bw-modelling-api

list_queries

Find BEx/BW queries built on CompositeProviders or ADSOs. Filter by InfoArea, InfoProvider, or name pattern to list reporting definitions.

Instructions

List BEx/BW Queries in the system.

Queries are reporting definitions built on top of CompositeProviders or ADSOs.

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

Input Schema

Name	Required	Description	Default
`info_area`	No	Filter by InfoArea technical name. Leave empty for all.
`max_results`	No	Maximum number of results (default: 200).
`search_term`	No	Filter by name pattern (supports * wildcard).	*
`info_provider`	No	Filter by InfoProvider (e.g. CompositeProvider or ADSO, such as "B080_V05"). This is the recommended way to list the queries built on a specific provider. Leave empty to search all.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, yet it reveals nothing about behavior: no read-only hint, no pagination behavior (max_results hints at limits but is not explained), no error/empty-result behavior, no performance caveats. Since this is a safe listing operation, a minimal read-only note would substantially improve it.

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 with the core purpose front-loaded, followed by a single clarifying clause. There is no filler or repetition; every sentence earns its place.

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?

The output schema exists, so return values need no explanation, and all parameters are schema-documented. The gaps are a missing behavioral note (no safe-read disclosure, given zero annotations) and no routing guidance against search_bw_objects or the other list_* siblings. For a listing tool of moderate complexity, this is adequate but leaves the sibling-differentiation question open.

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 the schema fully documents all four parameters — the baseline of 3 applies. The description adds only conceptual grounding (queries sit on CompositeProviders/ADSOs) which helps interpret the info_provider filter, but it does not add syntax or format details beyond the schema's own parameter descriptions.

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 ('List BEx/BW Queries in the system') and adds domain context ('Queries are reporting definitions built on top of CompositeProviders or ADSOs') that clarifies what queries are. It's clear, though it doesn't explicitly distinguish itself from sibling search_bw_objects, which could conceivably also surface queries.

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 main description offers no when-to-use or when-not-to-use guidance relative to siblings such as search_bw_objects or list_composite_providers. The only usage hint is buried inside the info_provider parameter description ('This is the recommended way to list the queries built on a specific provider'), which is not front-loaded and does not address the broader routing question.

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

Deploy Server