Skip to main content
Glama
CryLeech

jaicp-mcp

by CryLeech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

jaicp_call

Call JAICP/Tovie OpenAPI operations by spec ID and operation ID. Set confirm=true for write operations to require approval.

Instructions

Call a JAICP/Tovie OpenAPI operation by spec id + operationId. Writes need confirm=true unless JAICP_READ_ONLY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
pathNoExact OpenAPI path when operationId is duplicated
specYes
queryNo
confirmNoRequired true for mutating calls. Ignored when JAICP_READ_ONLY=true
headersNo
pathParamsNo
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Required true for create/update/delete and dialer addPhone GET"New value: +"Required true for mutating calls. Ignored when JAICP_READ_ONLY=true"
    • addedInput schema / properties / path
      Added value: +{
+  "description": "Exact OpenAPI path when operationId is duplicated",
+  "type": "string"
+}
    • addedInput schema / properties / query / additionalProperties / anyOf
      Added value: +[
+  {
+    "type": [
+      "string",
+      "number",
+      "boolean"
+    ]
+  },
+  {
+    "items": {
+      "type": [
+        "string",
+        "number"
+      ]
+    },
+    "type": "array"
+  }
+]
    • removedInput schema / properties / query / additionalProperties / type
      Removed value: -[
-  "string",
-  "number",
-  "boolean"
-]
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It discloses a key behavior: writes require confirm=true unless JAICP_READ_ONLY. However, it does not address error handling, authentication, rate limits, or return format, which are important for a complex tool.

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 primary purpose and adds a critical usage constraint. No filler or redundancy.

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?

The tool is complex with 8 parameters, nested objects, and no output schema. The description provides only the basic call mechanism and the confirm requirement. It lacks guidance on parameter construction, expected response, error conditions, or authentication, making it incomplete for an agent to use reliably.

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

Parameters2/5

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

Schema description coverage is low (25% – only path and confirm have descriptions). The description adds meaning for confirm (mutations require it) and clarifies that spec and operationId identify the operation, but it does not explain body, query, headers, or pathParams. Given the low coverage, the description should compensate more but only partially does.

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 states a clear action ('Call a JAICP/Tovie OpenAPI operation') and identifies the resource via 'spec id + operationId'. It is specific enough to distinguish from sibling tools that list specs or operations, though it does not explicitly name them.

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 description implies usage: this tool executes an operation, while siblings likely enumerate specs/operations. However, it does not explicitly state when to use it over alternatives, nor provide exclusions. The mention of confirm for writes hints at a usage condition but not a full guideline.

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