Skip to main content
Glama

ActivateDdl

Activates the specified CDS view (DDL source) so its inactive version becomes active. Use it to apply pending DDL changes in an SAP system.

Instructions

Activates the CDS view (DDL source) named by ddl_name, so its inactive version is in force. Recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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": {
      "ddl_name": "<ddl_name>"
    },
    "name": "ActivateDdl"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoHow much of the answer to return: "terse" (default, the fields you need to act), "full" (the whole parse), "raw" (the document as ADT sent it).terse
ddl_nameYesDDL source name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv20.1.0
    • removedInput schema / properties / session_id
      Removed value: -{
      -  "description": "Session ID from GetSession. If not provided, a new session will be created.",
      -  "type": "string"
      -}
    • removedInput schema / properties / session_state
      Removed value: -{
      -  "description": "Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.",
      -  "properties": {
      -    "cookie_store": {},
      -    "cookies": {
      -      "type": "string"
      -    },
      -    "csrf_token": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
  2. Changed2 schema fields changedv16.0.0
    • changedInput schema / properties / ddl_name / description
      Previous value: -"DDL source name (e.g., ZVW_MY_VIEW)."New value: +"DDL source name."
    • addedInput schema / properties / detail
      Added value: +{
      +  "default": "terse",
      +  "description": "How much of the answer to return: \"terse\" (default, the fields you need to act), \"full\" (the whole parse), \"raw\" (the document as ADT sent it).",
      +  "enum": [
      +    "terse",
      +    "full",
      +    "raw"
      +  ],
      +  "type": "string"
      +}
  3. Addedv8.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the core effect (the inactive version becomes active) and a non-obvious batch-mode behavior where calls are recorded and answered later by number, though it omits permission requirements and normal-mode return details.

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 is two sentences with no wasted words. The primary activation behavior is front-loaded, and the batch-mode caveat follows directly.

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?

For a mutation tool with no annotations and no output schema, it adequately explains the activation effect and batch behavior, but it does not describe what a non-batch call returns or how errors are surfaced. The description is minimally sufficient but has clear gaps.

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 coverage is 100%, so the schema already documents both parameters in detail. The description only names 'ddl_name' and adds no additional meaning beyond what the schema provides for either parameter.

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?

The description states a specific verb ('Activates') and resource ('CDS view (DDL source)') and explicitly names the parameter that identifies it. An agent can distinguish this from sibling activation tools like ActivateTable or ActivateProgram by the DDL/CDS scope.

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

Usage Guidelines3/5

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

It implies the tool should be used when an inactive version needs to be made active, but it does not explicitly say when to use this versus alternatives such as ActivateObjects or CheckDdl. No exclusions or prerequisites are given.

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