AIsa Stock Pulse

Quote published AIsa tools without executing them

batch_quote

Read-onlyIdempotent

Obtain AIsaServices cost quotes for 1 to 20 published tools without executing them. Same input as batch_use: exact tool names and schema-valid arguments. Never falls back to execution. The response reports auto_execute_eligible and auto_execute_threshold_micros_usd. auto_execute_eligible waives only the extra cost-confirmation step and does not override a user prohibition on execution, a narrower scope, or a tighter budget limit. Quotes are price observations, not authorization grants. 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": {
      "calls": "<calls>"
    },
    "name": "batch_quote"
  }
}

Input 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

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.
`auto_execute_eligible`	No	True when the worst-known total of successful USD quotes is at or below auto_execute_threshold_micros_usd. A non-USD successful quote makes the batch ineligible. Present on quote responses.
`auto_execute_threshold_micros_usd`	No	Configured auto-execute threshold in micro-USD. 0 disables automatic execution. Present on quote responses.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026
- changedOutput schema / properties / results / items / additionalProperties
```
Previous value: -falseNew value: +true
```
AddedOct 15, 2026
RemovedOct 15, 2026
AddedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish a safe, read-only, idempotent profile, but the description adds real behavioral context beyond them: no execution fallback, the meaning and limits of auto_execute_eligible (it waives only the cost-confirmation step, not a user prohibition, narrower scope, or tighter budget), and that quotes are not authorization grants. This is substantive disclosure that the annotations could not convey.

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?

Content is front-loaded: the purpose and the no-execution guarantee come first, then the response semantics, then calling conventions. The auto_execute_eligible caveat is dense but every clause constrains an actual agent decision, and the duplicated session_id sentence is the only minor redundancy.

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?

With an output schema present, the description needn't explain return values, yet it usefully interprets the two decision-relevant fields. For a nested calls array with 20-item batching and session correlation, the description covers naming, batching, and session reuse adequately; only search_id's role in correlation is left undocumented.

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 fills the most important gap by stating the tool-name convention (exact name as search returns it, no client prefix) and the 1–20 batch size, which the schema only encodes as min/maxItems. The session_id guidance merely repeats the schema text, and search_id is left entirely to the schema, so the added meaning is real but not exhaustive.

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 first sentence names a specific verb and resource (obtain cost quotes) plus scope (1 to 20 published tools) and the critical negative (without executing them). It also distinguishes itself from the sibling batch_use by noting they share the same input shape but differ in that this tool never falls back to execution.

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?

It clearly frames the tool as a pricing probe rather than an execution path ('Quotes are price observations, not authorization grants') and gives concrete rules for the call (exact tool names, no mcp__aisa__ prefix, reuse the Search session_id). What's missing is an explicit inverse pointer — it never says 'to actually execute, use batch_use' — so the routing is strongly implied rather than stated.

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

All AIsa Stock Pulse 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?