mcp-sac-tools

by pmankineni

Overview Schema Source Related Servers Discussions Admin

TypeScript

sac_create_team

Create a team in SAP Analytics Cloud and optionally add members by providing their user IDs.

Instructions

Create a new team in SAC with optional initial members.

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": {
      "displayName": "<displayName>"
    },
    "name": "sac_create_team"
  }
}

Input Schema

Name	Required	Description	Default
`memberIds`	No	Array of user IDs to add as members
`displayName`	Yes	Team name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 27, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. It only states 'Create a new team', implying mutation but provides no details on side effects, required permissions, idempotency, or behavior when the team 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?

The description is a single sentence with no extraneous words. It is front-loaded with the purpose and includes the optionality detail efficiently.

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

Completeness3/5

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

For a simple create tool with two parameters and no output schema, the description covers the basics. However, it lacks details on return value, error scenarios, and uniqueness constraints, which would be helpful for an agent.

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 the schema already documents both parameters adequately. The description adds the word 'optional' for initial members, which reinforces the schema but does not add significant new meaning.

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 (create) and resource (team), and it notes the optional initial members feature. It is distinct from siblings like sac_create_user, but does not explicitly differentiate from other create tools.

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 like sac_update_team or sac_list_teams. No mention of prerequisites, such as required permissions or whether the team name must be unique.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.