Skip to main content
Glama
Sign In
mcp-abap-keyword

mcp-abap-keyword

by yynhr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browse_main_topics

Get a categorized overview of ABAP Keyword Documentation sections and explore all main topics for quick navigation.

Instructions

Browse all main topics in the ABAP Keyword Documentation. Returns a categorized overview of available documentation sections.

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": "browse_main_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does mention that the tool 'returns a categorized overview', which adds some clarity about the output, but it does not describe limitations, pagination, language specifics, or what 'main topics' includes beyond the title.

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

Conciseness5/5

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

The description consists of two short, purposeful sentences. The first states the action and scope, and the second clarifies the expected result. There is no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter browse tool with no output schema, the description provides enough context to understand the tool's core purpose and what it returns. The phrase 'categorized overview of available documentation sections' is concise yet sufficient, though slightly more detail about the category structure could improve completeness.

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?

The tool has zero parameters, so there is nothing additional to explain about parameter usage or semantics. The baseline of 4 applies because no parameter information is needed.

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 uses a specific verb ('Browse') with a clear resource ('all main topics in the ABAP Keyword Documentation') and adds a return summary ('categorized overview'). It is clear enough to distinguish from search/lookup siblings, though it does not explicitly differentiate from the similarly scoped 'get_abap_subjects'.

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. It implies use for a high-level overview but does not state exclusions, prerequisites, or when to prefer a sibling tool like 'get_abap_subjects' or 'search_abap_keyword'.

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

Deploy Server

Other Tools