Skip to main content
Glama
Sign In
sap_analytics_cloud_mcp

sap_analytics_cloud_mcp

by JumenEngels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sac_teams_create

Create a team or group in SAP Analytics Cloud using SCIM v2. Specify group attributes and optionally create a team folder.

Instructions

Create a team/group (SCIM v2).

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": {
      "body": "<body>"
    },
    "name": "sac_teams_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesSCIM Group resource
allowalterationNoMust be true to execute
createTeamFolderNoCreate associated team folder

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; description only states 'Create' but lacks details on side effects, authentication needs, or the role of parameters like allowalteration and createTeamFolder.

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, concise sentence that front-loads the core action with no extraneous information.

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 no output schema and the presence of a nested object parameter, the description lacks information on return values, side effects, and prerequisites, making it insufficient for an agent to fully understand the tool's behavior.

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% and each parameter has a description, but the tool description adds no extra meaning beyond what is in the schema, especially for the complex nested 'body' parameter.

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 uses a specific verb (Create) and resource (team/group), clearly differentiating from siblings like sac_teams_list and sac_teams_patch.

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 context for invocation 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