Skip to main content
Glama
JumenEngels

sap_analytics_cloud_mcp

by JumenEngels

sac_export_delete_subscription

Delete data export subscriptions by specifying namespace, provider, and optional subscription ID. Choose to delete entire chains or all subscriptions for an entity set name.

Instructions

Delete data export subscription(s).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerIdYesProvider ID
deleteChainNoDelete entire chain
namespaceIdYesNamespace ID
subscriptionIdNoSubscription ID (empty = all for provider)
allowalterationNoMust be true to execute
deleteEntitySetNameNoDelete all for this EntitySetName
Behavior2/5

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

No annotations; description does not mention permissions, irreversibility, or the requirement that allowalteration must be true to execute (though schema mentions it). Missing critical behavioral context for a destructive operation.

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?

One concise sentence with no extraneous words; efficiently communicates the primary action.

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?

With 6 parameters, no output schema, and no annotations, the description is too terse. Does not explain behavior of deleteChain, deleteEntitySetName, or the critical allowalteration constraint.

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 covers 100% of parameters with descriptions; the tool description adds no additional meaning beyond what's in the schema. Baseline score of 3 is appropriate.

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 the verb 'Delete' and the resource 'data export subscription(s)', and distinguishes from sibling tools like create/get/list subscriptions.

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?

No guidance on when to use this tool vs alternatives, no prerequisites or conditions for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JumenEngels/sap_analytics_cloud_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server