Skip to main content
Glama
Sign In
sap_analytics_cloud_mcp

sap_analytics_cloud_mcp

by JumenEngels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sac_stories_copy

Duplicate an SAP Analytics Cloud story by providing its source ID. Optionally set target folder and new name; confirmation required.

Instructions

Copy a story.

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": {
      "sourceStoryId": "<sourceStoryId>"
    },
    "name": "sac_stories_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
newNameNoName for copy
copyToFolderNoTarget folder
sourceStoryIdYesSource story ID
allowalterationNoMust be true to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations, the description must fully disclose behavioral traits. It fails to mention that 'allowalteration' must be true for execution, nor does it describe side effects, permissions, or what happens to linked content.

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

Conciseness2/5

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

The description is extremely short but underspecified. It lacks essential detail, crossing from conciseness into inadequacy. Every sentence should earn its place; this single sentence does not.

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

Completeness1/5

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

Given 4 parameters, no output schema, and no annotations, the description is completely incomplete. It does not explain the copy behavior (deep copy?), naming conventions, folder target, or any return information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds no value beyond the minimal schema descriptions. It does not clarify ambiguous parameters like 'copyToFolder' (path vs. ID) or the interaction between 'newName' and default naming.

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

Purpose1/5

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

The description 'Copy a story.' is a tautology of the tool name. It does not specify what kind of story (SAP Analytics Cloud?), nor does it differentiate from sibling tools like sac_stories_delete or sac_stories_rename.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context for copying, or scenarios where other tools would be more appropriate.

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