Skip to main content
Glama
Sign In
b1-mcp-server

b1-mcp-server

by Anand95r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

execute_service_layer

Executes read-only OData GET requests against the connected SAP Business One Service Layer to retrieve data; use the write tool for PATCH, POST, or DELETE operations.

Instructions

Execute a read-only OData GET against the currently connected SAP Business One Service Layer. Writes go through execute_service_layer_write.

Denied when the connected profile's slAllowedMethods (printed by connect_database) omits GET. Query options are allowed; absolute URLs, Login/Logout and $batch are denied.

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": {
      "url": "<url>"
    },
    "name": "execute_service_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRelative OData endpoint without the configured /b1s/v1/ or /b1s/v2/ root
methodNoAlways GET. PATCH, POST and DELETE go through execute_service_layer_writeGET

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden; it discloses that the tool is read-only, that access is gated by slAllowedMethods, and that certain endpoint classes are rejected. It does not cover response shape, pagination, or error behavior for a denied GET, which keeps it short of a 5.

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?

Two short paragraphs with the core capability front-loaded, followed by the permission and rejection constraints. No sentence is redundant, and the sibling hand-off is stated in a single clause.

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

Completeness4/5

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

With 2 parameters, no output schema, and no annotations, the definition covers the essentials: what it does, what it refuses, and how permissions gate it. The main remaining gap is that the OData response shape and failure modes are not described, though for a thin passthrough this is a minor omission.

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%, and the schema already explains that url is relative without the /b1s/v1 or /b1s/v2 root and that method is a fixed GET. The description repeats the write-routing rule but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 first sentence names a specific verb (Execute), a specific resource class (read-only OData GET), and the target system (SAP Business One Service Layer), and the second sentence explicitly routes writes to execute_service_layer_write. An agent can distinguish this from the write sibling without opening either schema.

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

Usage Guidelines5/5

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

It states the positive case (read-only GET, query options allowed), the alternative (writes go through execute_service_layer_write), and concrete exclusions (absolute URLs, Login/Logout, $batch are denied). It also gives the precondition that the profile's slAllowedMethods must include GET and points to connect_database for that check.

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