SAP OData MCP Server

sap_query_entity_set

Query SAP OData entity sets with filtering, sorting, and pagination to retrieve structured business data from SAP systems.

Instructions

Query an OData entity set with filtering, sorting, and pagination

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": {
      "serviceName": "<serviceName>",
      "entitySet": "<entitySet>"
    },
    "name": "sap_query_entity_set"
  }
}

Input Schema

Name	Required	Description
`serviceName`	Yes	Name of the OData service
`entitySet`	Yes	Name of the entity set
`select`	No	Fields to select
`filter`	No	OData filter expression
`orderby`	No	OData orderby expression
`top`	No	Number of records to return
`skip`	No	Number of records to skip
`expand`	No	Navigation properties to expand

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Feb 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states basic functionality without disclosing behavioral traits. It lacks details on authentication needs, rate limits, error handling, or response format (e.g., JSON structure, pagination behavior). This is inadequate for a query tool with complex parameters.

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?

The description is a single, efficient sentence that front-loads the core purpose and key capabilities. It wastes no words and is appropriately sized for the tool's complexity, making it easy for an agent to parse quickly.

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 (8 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain return values, error cases, or how parameters interact (e.g., OData syntax for 'filter'), leaving significant gaps for an agent to invoke the tool correctly in a real SAP OData context.

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 fully documents all 8 parameters. The description adds no additional meaning beyond implying support for filtering, sorting, and pagination—which is already evident from parameter names like 'filter', 'orderby', 'top', and 'skip'. Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('Query') and target ('OData entity set') with specific capabilities ('filtering, sorting, and pagination'). It distinguishes from siblings like sap_create_entity or sap_delete_entity by focusing on read operations, though it doesn't explicitly differentiate from sap_get_entity which might also retrieve data.

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?

No explicit guidance on when to use this tool versus alternatives like sap_get_entity or sap_get_service_metadata. The description implies usage for querying with advanced options but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to infer based on parameter names alone.

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

Deploy Server