Skip to main content
Glama
Sign In
sap_analytics_cloud_mcp

sap_analytics_cloud_mcp

by JumenEngels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sac_stories_rename

Rename a story in SAP Analytics Cloud by specifying the story ID and new name. Requires confirmation to execute.

Instructions

Rename 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": {
      "storyId": "<storyId>",
      "newName": "<newName>"
    },
    "name": "sac_stories_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
newNameYesNew name
storyIdYesStory ID
allowalterationNoMust be true to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The description does not disclose any behavioral traits beyond what the input schema provides. It does not mention that the tool mutates data, requires the 'allowalteration' flag, or any side effects. With no annotations, the description carries the full burden but fails to add value.

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 concise (one sentence) but lacks important details such as the requirement for 'allowalteration' to be true. It is under-specified rather than efficiently concise.

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?

Given three parameters and no output schema, the description is incomplete. It does not explain the role of 'allowalteration' or the renaming behavior. The description is minimal and leaves gaps.

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 covers all three parameters with descriptions, achieving 100% coverage. The baseline score is 3, and the description adds no further semantic value beyond the schema.

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 'Rename a story' clearly states the action and resource. It is a specific verb and resource, and it distinguishes from sibling tools like copy, delete, and list, as renaming is unique. However, it could be improved by mentioning the required flag.

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 is provided on when to use this tool versus alternatives, such as when to rename vs. copy or delete. There are no prerequisites or conditions mentioned. The description lacks any explicit usage context.

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