Skip to main content
Glama
bpamiri

u2-mcp

by bpamiri

call_subroutine

Execute cataloged BASIC subroutines with arguments by reference, returning output arguments for MultiValue database operations.

Instructions

Call a cataloged BASIC subroutine with arguments.

Executes a cataloged BASIC program and returns the results. Arguments are passed by reference, so output arguments will be returned in the response.

Args: name: Name of the cataloged subroutine args: List of argument values to pass (input arguments). Arguments are passed as strings and converted by the subroutine. num_args: Total number of arguments the subroutine expects. If not specified, uses len(args). Required if subroutine has output-only arguments.

Returns: Dictionary containing: - status: success or error - args_out: List of argument values after subroutine execution - original_args: The input arguments that were passed

Example: # Call GET.CUSTOMER.DATA with customer ID, returns data in args 2-3 call_subroutine("GET.CUSTOMER.DATA", ["CUST001", "", ""], num_args=3)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNo
nameYes
num_argsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations, the description carries full burden. It explains pass-by-reference behavior and the role of num_args, but does not disclose side effects, permissions, or error conditions. The return format is described, but deeper behavioral traits are missing.

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 concise yet complete, with a clear opening sentence followed by detailed parameter explanations and a helpful example. Every sentence adds value, and the structure is easy to scan.

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?

Given the tool's complexity and the presence of an output schema, the description covers the main behavioral aspects (pass-by-reference, num_args usage, and return values). It could mention prerequisites or error handling, but overall it is sufficient for an agent's understanding.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully explains each parameter: name as the subroutine name, args as input argument strings converted by the subroutine, and num_args as the expected count (defaults to len(args), required for output-only args). This adds significant meaning beyond the raw schema.

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 clearly states the tool calls a cataloged BASIC subroutine with arguments, using specific verbs and naming the resource. It distinguishes itself from sibling tools like execute_query and execute_tcl by being about subroutines, not queries or TCL commands.

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 does not provide guidance on when to use this tool versus alternatives. There is no mention of scenarios where it is preferred or when not to use it, leaving the agent without decision-making context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bpamiri/u2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server