Skip to main content
Glama
Sign In
sap_analytics_cloud_mcp

sap_analytics_cloud_mcp

by JumenEngels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sac_import_validate_job

Validates an import job by ID to check its readiness before execution, preventing errors in SAP Analytics Cloud imports.

Instructions

Validate import job before running.

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": {
      "jobId": "<jobId>"
    },
    "name": "sac_import_validate_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesJob ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose whether the validation is read-only, what checks are performed, or any side effects, leaving the agent uninformed about behavioral traits.

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, efficient sentence that conveys the core purpose. While concise, it could benefit from slight expansion to improve clarity without becoming verbose.

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 the tool's complexity (no output schema, single parameter), the description is incomplete. It lacks information about validation outcomes, error handling, or any post-validation steps, which an agent would need for proper invocation.

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 description coverage is 100% for the single parameter 'jobId', and the description adds no additional semantics beyond 'Job ID'. Baseline 3 is appropriate as the schema already documents the parameter adequately.

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 tool validates an import job before execution, which distinguishes it from sibling tools like sac_import_run_job. However, it could be more specific about what 'validate' entails.

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

Usage Guidelines3/5

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

The phrase 'before running' implies usage context, but there is no explicit guidance on when not to use this tool or mention of alternatives like sac_import_get_job_status for checking validation results.

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