Skip to main content
Glama
Sign In
sap_analytics_cloud_mcp

sap_analytics_cloud_mcp

by JumenEngels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sac_multi_action_execute

Execute a multi action in SAP Analytics Cloud by providing its package:object ID and optional parameter values.

Instructions

Execute a multi action. ID format: :. Body requires parameterValues array (empty if none).

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": {
      "multiActionId": "<multiActionId>"
    },
    "name": "sac_multi_action_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
multiActionIdYesID as packageId:objectId, e.g. t.TEST:CEEFOKMRUKJBY5BN47F1NS2L8G
allowalterationNoMust be true to execute
parameterValuesNoParameters array, empty [] if none required

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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. It only states 'Execute' without detailing side effects, permissions, rate limits, or post-execution behavior. This is insufficient for a mutation tool.

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, front-loaded with the verb and resource, and every sentence adds necessary information. No wasted words.

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

Completeness2/5

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

There is no output schema, so the description should indicate return values or execution outcome. It does not. The tool's behavior and error conditions are also omitted, making it incomplete for an 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?

Schema coverage is 100%, so baseline is 3. The description adds the ID format for multiActionId and notes the parameterValues array requirement, but these are also covered in the schema descriptions. Little additional meaning is provided.

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 clearly states 'Execute a multi action' and specifies the ID format. This distinguishes it from sibling tools like sac_multi_action_get_status, which retrieves status rather than executing.

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?

The description provides the ID format and body requirements but does not explicitly state when to use this tool versus alternatives. Usage is implied but not guided with when-not or exclusion criteria.

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