Skip to main content
Glama
Sign In
sap_analytics_cloud_mcp

sap_analytics_cloud_mcp

by JumenEngels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sac_export_get_subscription

Retrieves a subscription using namespace, provider, and subscription IDs.

Instructions

Get subscription by composite key.

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>",
      "subscriptionId": "<subscriptionId>"
    },
    "name": "sac_export_get_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerIdYesProvider ID
namespaceIdYesNamespace ID
subscriptionIdYesSubscription ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only says 'Get', implying a read-only operation, but does not disclose any behavioral traits such as side effects, permissions, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no filler. For a straightforward get operation, this is efficient, though it could be slightly more informative.

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?

The tool has no output schema and the description does not indicate what the return value will be. Given the simplicity of the tool (3 required params), the description is incomplete by not clarifying the response format or content.

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?

The input schema has 100% description coverage for all three parameters. The tool description adds no extra meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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

Purpose4/5

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

The description clearly states the action (get) and the resource (subscription) with the phrase 'by composite key', which distinguishes it from list/create/delete siblings. However, it does not explicitly name the key fields, which are only visible in the schema.

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 versus alternatives like sac_export_list_subscriptions or sac_export_create_subscription. The description provides no context for selection.

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