AIsa Equities

Get AIsa tool schemas in one batch

batch_get_schema

Read-onlyIdempotent

Retrieve schemas for 1 to 20 exact tool names from search. Build arguments from successful schemas, then call batch_quote. Do not call batch_use yet. 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.

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": {
      "tools": "<tools>"
    },
    "name": "batch_get_schema"
  }
}

Input Schema

Name	Required	Description
`tools`	Yes	Exact tool names returned by search whose complete contracts are needed. Never invent tool names.
`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.
`include_documentation`	No	Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support.
`include_response_schema`	No	Return the complete response_schema. Defaults to false.
`include_arguments_schema`	No	Return the complete arguments_schema. Defaults to true.

Output Schema

Name	Required	Description
`tools`	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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 4, 2026

changedOutput schema / properties / tools / additionalProperties / additionalProperties
```
Previous value: -falseNew value: +true
```
addedOutput schema / properties / tools / additionalProperties / properties / execution_supported / anyOf
```
Added value: +[
+  {
+    "type": "null"
+  },
+  {
+    "type": "boolean"
+  }
+]
```
removedOutput schema / properties / tools / additionalProperties / properties / execution_supported / type
```
Removed value: -"boolean"
```
addedOutput schema / properties / tools / additionalProperties / properties / execution_unsupported_reason / anyOf
```
Added value: +[
+  {
+    "type": "null"
+  },
+  {
+    "type": "string"
+  }
+]
```
removedOutput schema / properties / tools / additionalProperties / properties / execution_unsupported_reason / type
```
Removed value: -"string"
```

addedOutput schema / properties / tools / additionalProperties / properties / runtime_availability

Added value: +{
+  "anyOf": [
+    {
+      "type": "null"
+    },
+    {
+      "enum": [
+        "enabled",
+        "disabled",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  ],
+  "description": "Live availability observed within the discovery budget. Unknown retains the active published Catalog schema, which may be stale relative to live status; it does not authorize execution. Quote and use perform strict runtime checks."
+}

AddedOct 15, 2026
RemovedOct 15, 2026
AddedOct 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds the genuinely useful disclosure that omitting session_id creates a new session and that this call is a prerequisite to batch_quote. It does not discuss failure behavior for unknown tool names, which would be the remaining gap.

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

Conciseness4/5

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

Four short, front-loaded sentences sequenced in execution order (what to fetch, what to do next, naming rules, session handling). The session_id sentence duplicates the schema text and could be dropped without loss.

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?

An output schema exists, so return values need no explanation, and the multi-step position of this tool in the search-to-quote pipeline is spelled out. What is missing is how partial or unknown tool names in the batch are handled, which matters for a batch tool with a 20-item cap.

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 100%, so the baseline is 3, but the description earns more by adding meaning the schema lacks: the exact-name/no-client-prefix rule and the instruction that session_id must be carried across all calls in the task. It restates the session_id creation behavior verbatim from the schema, which is redundant but harmless.

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?

States a specific verb (retrieve) and resource (schemas) with an explicit scope bound: 1 to 20 exact tool names that came from search. It distinguishes itself from the sibling 'search' tool by making clear it consumes names rather than discovering them.

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?

Gives explicit workflow ordering against named siblings: build arguments from successful schemas, then call batch_quote, and do not call batch_use yet. It also names the input source (search) and the naming constraint (no mcp__aisa__ prefix), leaving little to inference.

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

All AIsa Equities 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?