Skip to main content
Glama

run_bpj_ai_tool

Read-onlyIdempotent

Run a BPJ suite tool found through list_bpj_ai_tools. Pass its exact freeMcp name and arguments matching its inputSchema.

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": {
      "name": "<name>",
      "arguments": "<arguments>"
    },
    "name": "run_bpj_ai_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact freeMcp name returned by discovery.
argumentsYesTool-specific inputs from its inputSchema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds the discovery prerequisite and the exactness requirement on the name, but says nothing about failure behavior for an unknown name or malformed arguments, nor whether the invoked tool's own side effects are governed by the wrapper's read-only annotation.

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 sentences, zero filler, with the discovery dependency front-loaded before the invocation instructions. Every clause carries actionable information.

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

Completeness3/5

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

Adequate for a two-parameter dispatcher whose schema and annotations are rich, and no output schema exists so return values need no explanation. However, for a meta-tool that proxies arbitrary siblings, the description omits error semantics and any statement about how the target tool's inputs and effects relate to this wrapper's read-only annotation.

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 both parameters and the name pattern are already documented in the schema. The description reinforces that the name must be the exact freeMcp name from discovery and that arguments must match the target tool's inputSchema, which is useful but largely restates the schema.

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?

States a specific verb and resource: run a BPJ suite tool, and ties it to the discovery tool list_bpj_ai_tools. An agent can tell this is the generic dispatcher rather than one of the concrete bpj_* siblings, though it doesn't characterize what the dispatched tools collectively do.

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

Usage Guidelines4/5

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

Gives an explicit two-step workflow: discover the tool via list_bpj_ai_tools, then invoke it here with the exact freeMcp name and matching arguments. It does not state when to prefer a direct call or what to do when no discovered tool fits, so there are no explicit exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.