Skip to main content
Glama
Sign In

Krusgraph

by com.krusgraph
OverviewDiscussions(1)Admin

Show which SAP tables and relationships the SAP pack recognises (nothing created)

sap_pack_draft
Read-only

Shows which tables of the source the SAP pack recognises (VBAK, VBAP, LIKP, VBRK, KNA1…, with or without a prefix such as sap_), their keys with MANDT, the order-to-cash relationships it applies with the public source of each, the ones it lists but does not apply (VBFA), missing pack tables and columns, and the traps (client, header vs item amounts, currency, leading zeros, partner functions). Requires workspace and source. Returns JSON, with the chosen export when export is not "none". Read-only; changes nothing. Errors: {error, kind, hint}.

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": {
      "workspace": "<workspace>",
      "source": "<source>"
    },
    "name": "sap_pack_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNoKey overrides as in plan_backend, {table: [columns]}; they win over the pack. Default none. Example: {"vbap": ["mandt", "vbeln", "posnr"]}.
exportNo"none" (default), or one export of the plan: "krusgraph" (keys/confirmed), "dab" (Data API builder config), "extraction" (tables, keys, delta columns) or "dbt". Example: "dbt".none
schemaNoSchema with the SAP tables, as the mirroring or pipeline named it. Default "dbo". Example: "sap".dbo
sourceYesLakehouse, warehouse or SQL database, name or id.
variantNo"ecc" or "s4hana" to consider only that variant's tables. Default: the tables present decide. Example: "s4hana".
confirmedNoConfirmed relationships as in plan_backend; they win over the pack. Default none. Example: [{"source": "vbap", "source_cols": ["mandt", "vbeln"], "target": "vbak", "target_cols": ["mandt", "vbeln"]}].
workspaceYesFabric workspace, name or id.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, and the description reinforces that with 'Read-only; changes nothing.' It adds useful behavior: JSON return shape, export behavior, and an error shape ({error, kind, hint}); it does not cover auth or rate limits, but with annotations present this is solid transparency.

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 purpose is front-loaded and every sentence carries relevant content. The first sentence is dense and long, and 'Read-only; changes nothing' slightly repeats the annotations, but there is no real waste.

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

Completeness5/5

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

Given the output schema and full schema coverage, the description supplies the additional context an agent needs: required inputs, return format, error format, and the domain traps the report exposes. Nothing essential for correct invocation appears to be missing.

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%, so the schema already explains all seven parameters. The description adds only that workspace and source are required and that export affects the return, without elaborating on keys, confirmed, or variant beyond what the schema provides.

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?

The description uses a specific verb ('Shows') and a precise resource ('which tables of the source the SAP pack recognises'), then enumerates the scope: keys, MANDT, relationships, missing tables, and traps. This is clearly distinct from planning or relationship-suggestion siblings.

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?

It states the prerequisites ('Requires workspace and source') and implies use for inspecting SAP pack recognition, but it gives no explicit when-to-use guidance or alternatives. It never tells the agent when to prefer this over plan_backend or suggest_relationships.

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

All Krusgraph toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources