Skip to main content
Glama
Sign In
sap_analytics_cloud_mcp

sap_analytics_cloud_mcp

by JumenEngels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sac_export_create_subscription

Set up a data export subscription to track delta changes in SAP Analytics Cloud by specifying namespace, provider, and entity set.

Instructions

Create data export subscription for delta tracking.

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": {
      "NamespaceID": "<NamespaceID>",
      "ProviderID": "<ProviderID>",
      "EntitySetName": "<EntitySetName>"
    },
    "name": "sac_export_create_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
FilterNoOData filter
SelectionNoComma-separated dims/measures for FactDataAggregation
ExternalIDNoUnique external ID for subscription chain
ProviderIDYesProvider ID
DescriptionNoDescription
NamespaceIDYesNamespace ID
EntitySetNameYesEntity set to track
allowalterationNoMust be true to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states 'create' with no details on mutation behavior, idempotency, permissions, or side effects (e.g., what happens if subscription already exists).

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?

Single sentence with no unnecessary words. Front-loaded with verb and resource. Every part earns its place.

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?

Despite clear purpose, description lacks return value details, error conditions, or behavior for the 8 parameters (especially complex ones like EntitySetName). Incomplete for a subscription creation tool.

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. Description adds no additional semantics beyond the parameter descriptions in the schema. No extra context on typical usage or constraints.

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 clearly states the action ('Create') and the resource ('data export subscription') with specific purpose ('delta tracking'). Distinguishes from sibling tools like sac_export_delete_subscription and sac_export_get_subscription.

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 (e.g., when to create vs update a subscription). No prerequisites, conditions, or exclusion criteria mentioned.

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