4d-mcp

callFunction

Invoke ORDA class functions on 4D servers using target interface, function name, and optional parameters.

Instructions

Call an ORDA class function on the 4D server

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": {
      "target": "<target>",
      "func": "<func>"
    },
    "name": "callFunction"
  }
}

Input Schema

Name	Required	Description
`func`	Yes	Function name to call
`params`	No	Array of parameters to pass to the function
`target`	Yes	Target interface (dataclass name or other interface)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.2/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full burden. It fails to disclose side effects, permission requirements, error behavior, or return value characteristics. Calling an arbitrary class function could have unknown effects, and the description gives no hint of that.

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, compact sentence with no filler. It front-loads the verb and resource, making the purpose immediately clear.

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 tool that can invoke arbitrary server-side functions, this description is insufficient. With no output schema, no annotations, and no mention of return values, side effects, or errors, an agent has too little context to understand the tool's full behavior.

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?

The input schema provides descriptions for all three parameters (target, func, params), covering 100% of them. The description itself adds nothing beyond the schema, so the baseline score of 3 is appropriate.

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 ('Call') with a clear resource ('ORDA class function') and context ('on the 4D server'). It distinguishes itself from sibling CRUD tools like query, upsert, and delete by focusing on function invocation.

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?

The usage is implied: it is for calling ORDA class functions. However, there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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

Deploy Server