Skip to main content
Glama
Sign In
sap-integration-suite-mcp

sap-integration-suite-mcp

by rameshvaranganti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_iflow_status

Read-onlyIdempotent

Retrieve the runtime status of a specified SAP Cloud Integration flow; return an explicit unavailable result when status cannot be retrieved.

Instructions

Retrieve runtime artifact status, or an explicit unavailable result.

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": {
      "integrationFlow": "<integrationFlow>"
    },
    "name": "get_iflow_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
integrationFlowYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds a modest behavioral detail that an unavailable result can be returned explicitly, but omits auth, rate limits, and what 'status' actually contains.

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?

It is a single short sentence with no filler, and the retrieval verb is front-loaded. However, the cryptic 'runtime artifact' phrasing means brevity comes at the cost of precision.

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?

For a one-parameter getter with no output schema, the description should explain what status values mean and what an unavailable result looks like. It does neither, and it also leaves the required parameter undocumented, so it is incomplete for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% and the sole required parameter 'integrationFlow' is not mentioned in the description at all. No meaning, format, or pattern guidance is added to compensate.

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

Purpose3/5

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

The description gives a verb ('Retrieve') and a resource ('runtime artifact status'), but 'runtime artifact' is vague jargon that is not clearly tied to the integration flow concept in the tool name or parameter. It also fails to distinguish this tool from sibling health/failure/message 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?

There is no guidance on when to use this tool versus alternatives like summarize_integration_health or get_recent_failures. The only extra qualification concerns unavailable results, which describes output behavior rather than 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