abapsmith

abap_fluid

Read-onlyIdempotent

Deploy and run small generated ABAP tools inside the ABAPSMITH_FLUID_API environment. Writes are locked until ABAP_ALLOW_WRITE=true is set on the server.

Instructions

Deploy and run small generated ABAP tools inside $ABAPSMITH_FLUID_API. LOCKED on this server: ABAP_ALLOW_WRITE does not enable writes, and ABAP_MODE is not set, so that variable is what decides it. Set ABAP_ALLOW_WRITE=true (ABAP_ALLOW_PACKAGES is optional — it narrows the default, which is every package). Calling it returns a refusal and sends nothing to the SAP system.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "abap_fluid"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.5.6Sep 12, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful context that the tool is locked and returns a refusal without contacting the SAP system, but it is internally confusing about whether setting ABAP_ALLOW_WRITE=true would enable writes. It does not contradict the annotations directly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph with ambiguous pronouns and contradictory statements about locking versus enabling writes. The key locked/refusal behavior is not front-loaded cleanly, and several clauses do not earn their place for a zero-parameter tool.

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 zero parameters, rich annotations, and no output schema, the description needs only to explain the tool's actual effect. It does say the call is refused and nothing is sent to SAP, but the contradictory deploy/run framing and unclear env-var instructions leave the agent without a coherent picture of when or why to use it.

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

Parameters4/5

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

The tool takes zero input parameters, so the baseline score is 4. The description mentions environment variables rather than input arguments, and the schema itself is empty with 100% coverage.

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 opening sentence states a specific verb and resource: 'Deploy and run small generated ABAP tools inside $ABAPSMITH_FLUID_API.' However, the subsequent claim that calling it returns a refusal and sends nothing to the SAP system conflicts with the stated deploy/run purpose, leaving the effective purpose muddled. No sibling differentiation is provided.

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?

The description discusses environment variables such as ABAP_ALLOW_WRITE and ABAP_ALLOW_PACKAGES, but gives no clear when-to-use guidance or named alternatives among the many abap_* siblings. The instructions are further undermined by the statement that calling the tool is refused on this server.

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