AIsa Social

Execute published AIsa tools

batch_use

Destructive

Billable API calls can incur substantial charges. Never call before a successful batch_quote for the same tools and arguments. Execute only when that quote response reports auto_execute_eligible=true for these calls, or when explicit user authorization covers that cost and risk. auto_execute_eligible waives only the extra cost-confirmation step; it does not override a user prohibition on execution, a narrower scope, or a tighter budget limit. Re-quote if tools, arguments, or scope change. Execute 1 to 20 independent published-tool calls; never silently retry. A missing or failed quote is not free. Use tool names exactly as search returns them, without a client prefix such as mcp__aisa__. Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.

Input Schema

TableJSON Schema

Name	Required	Description
`calls`	Yes
`search_id`	No	Optional search correlation identifier returned by search.
`session_id`	No	Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.

Output Schema

TableJSON Schema

Name	Required	Description
`results`	Yes
`batch_id`	Yes
`session_id`	Yes	Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.
`error_count`	Yes
`total_count`	Yes
`success_count`	Yes
`next_steps_guidance`	Yes	Deterministic next-step instructions derived from this result. Not an authorization grant.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedOct 15, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / properties / calls / description

Removed value: -"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch"

addedInput schema / properties / calls / items / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / calls / items / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / calls / items / properties

Added value: +{
+  "arguments": {
+    "additionalProperties": true,
+    "description": "Strictly schema-compliant arguments using the exact field names and types from this tool's arguments_schema.",
+    "type": "object"
+  },
+  "call_id": {
+    "description": "Caller-chosen identifier unique within this batch.",
+    "maxLength": 128,
+    "minLength": 1,
+    "type": "string"
+  },
+  "tool": {
+    "description": "Exact tool name returned by search or batch_get_schema. Never invent a name.",
+    "minLength": 1,
+    "type": "string"
+  }
+}

addedInput schema / properties / calls / items / required

Added value: +[
+  "call_id",
+  "tool",
+  "arguments"
+]

addedInput schema / properties / calls / maxItems
```
Added value: +20
```
addedInput schema / properties / calls / minItems
```
Added value: +1
```

removedInput schema / properties / max_price_usd

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Per-call price cap applied to every item"
-}

removedInput schema / properties / search_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / search_id / default
```
Removed value: -null
```

changedInput schema / properties / search_id / description

Previous value: -"search_id from the search that found these operations"New value: +"Optional search correlation identifier returned by search."

addedInput schema / properties / search_id / type
```
Added value: +"string"
```

addedInput schema / properties / session_id

Added value: +{
+  "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+  "maxLength": 128,
+  "pattern": "^[A-Za-z0-9_-]*$",
+  "type": "string"
+}

addedOutput schema / $defs

Added value: +{
+  "jsonValue": {
+    "anyOf": [
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/jsonValue"
+        },
+        "type": "object"
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/jsonValue"
+        },
+        "type": "array"
+      },
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "JSON value returned by the upstream tool."
+  }
+}

addedOutput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties

Added value: +{
+  "batch_id": {
+    "type": "string"
+  },
+  "error_count": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "next_steps_guidance": {
+    "description": "Deterministic next-step instructions derived from this result. Not an authorization grant.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "results": {
+    "items": {
+      "$schema": "https://json-schema.org/draft/2020-12/schema",
+      "additionalProperties": false,
+      "properties": {
+        "call_id": {
+          "type": "string"
+        },
+        "customer_cost_micros_usd": {
+          "description": "Actual customer charge settled by AIsaServices, in micro-USD. Omitted when the upstream response does not report it.",
+          "minimum": 0,
+          "type": "integer"
+        },
+        "data": {
+          "$ref": "#/$defs/jsonValue"
+        },
+        "error": {
+          "anyOf": [
+            {
+              "$schema": "https://json-schema.org/draft/2020-12/schema",
+              "additionalProperties": false,
+              "properties": {
+                "message": {
+                  "type": "string"
+                },
+                "retryable": {
+                  "type": "boolean"
+                },
+                "status": {
+                  "type": "integer"
+                },
+                "type": {
+                  "enum": [
+                    "validation",
+                    "authentication",
+                    "payment",
+                    "permission",
+                    "rate_limit",
+                    "upstream",
+                    "timeout",
+                    "internal"
+                  ],
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type",
+                "status",
+                "retryable"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "request_id": {
+          "type": "string"
+        },
+        "successful": {
+          "type": "boolean"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "upstream_status": {
+          "description": "HTTP status returned by AIsaServices when a request was dispatched.",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "call_id",
+        "tool",
+        "successful",
+        "request_id"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "session_id": {
+    "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+    "maxLength": 128,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9_-]*$",
+    "type": "string"
+  },
+  "success_count": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "total_count": {
+    "minimum": 1,
+    "type": "integer"
+  }
+}

addedOutput schema / required

Added value: +[
+  "session_id",
+  "batch_id",
+  "total_count",
+  "success_count",
+  "error_count",
+  "results",
+  "next_steps_guidance"
+]

First observedSep 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover mutability, destructiveness, and open-world behavior. The description adds critical business logic: billable calls, quote dependency, the meaning of auto_execute_eligible (waives only cost confirmation, not user prohibitions), and no silent retry. It doesn't detail rate limits or return format, but with an output schema present, that's acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and front-loads the cost warning, but it packs many separate instructions into one block, making it less scannable. Some sentences like 'A missing or failed quote is not free' add value, but the overall flow could be better structured.

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 destructive, open-world annotations and the presence of an output schema, the description covers the essential preconditions and behavioral constraints. It could mention error handling or partial failure behavior, but the core guidance is sufficient for correct invocation.

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

Parameters4/5

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

Schema coverage is 67%, and the description adds important semantics: tool names must be exact without client prefix, session_id reuse guidance, and 1-20 call limit. It doesn't explain search_id, but the schema description for search_id is already clear enough.

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 verb and resource: 'Execute 1 to 20 independent published-tool calls', and the title matches. It distinguishes itself from batch_quote by requiring a quote first, but doesn't explicitly contrast with the singular 'use' sibling, though that's implied by 'batch'.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use and when-not-to-use conditions: only after a successful batch_quote with auto_execute_eligible=true or explicit user authorization. It also states re-quote conditions and prohibits silent retries, leaving little ambiguity.

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

All AIsa Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?