Skip to main content
Glama
Sign In
mcp-rap-migrator

mcp-rap-migrator

by sharmarhl1994-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_released_cds

Verify which tables have released SAP CDS views to enable Clean Core access, then pass the mapping to generate RAP skeleton.

Instructions

STEP 1b — MANDATORY before generate_rap_skeleton. Checks if SAP has released CDS views for the tables found in the Module Pool. Clean Core: always SELECT from released CDS instead of raw tables. Returns cds_source_mapping to pass into generate_rap_skeleton.

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": {
      "tables": "<tables>"
    },
    "name": "check_released_cds"
  }
}

Input Schema

NameRequiredDescriptionDefault
tablesYesTables from analyze_module_pool e.g. VBAK,VBAP,KONV

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description must cover behavior. It states checks and returns mapping, which implies read-only. Could add details about side effects or permissions, but for a check tool this is acceptable.

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?

Two sentences plus a key annotation about Clean Core. Front-loaded with step number and mandatory nature. Every sentence adds value, no redundancy.

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

Completeness5/5

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

Given single parameter and no output schema, description fully explains purpose, input, output ('returns cds_source_mapping'), and workflow position. No gaps for AI agent.

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?

Only one parameter 'tables' with schema description already good (100% coverage). Description adds context that these come from analyze_module_pool, but no new syntax or format details beyond schema.

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

Purpose5/5

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

Description uses specific verb 'checks if SAP has released CDS views' and resource 'tables from Module Pool'. Mandatory step before generate_rap_skeleton distinguishes it from siblings like analyze_module_pool and generate_rap_skeleton.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly labeled 'STEP 1b — MANDATORY before generate_rap_skeleton' and gives rationale about Clean Core. Does not explicitly state when not to use, but context implies after analyze_module_pool.

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