Your agent needs the two halves of a move at once — what people are posting about a ticker right now, and what the price and the news actually did.
What you can ask for • "What is X saying about $NVDA today, and what did the stock do?" • "Show the chatter and the price move for these five tickers side by side." • "Which tickers are being talked about most right now?" • "Pull the news and the snapshot behind this spike."
How to use it Point any MCP client at https://mcp.aisa.one/stock-pulse/mcp and sign in with OAuth — there is no key to create or paste. 4 tools: a combined stock-pulse call that joins X/Twitter chatter to the tickers mentioned, plus advanced tweet search, price snapshots and financial news.
Why this rather than the source One call instead of four, with the join already done.
It is also a door to the rest The same login reaches 26 sources and 580+ operations. Spot the move here, then ask the same agent for the filings or the fundamentals behind it — without adding a second server.
What it costs Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident.
Where else it reaches https://mcp.aisa.one/finance/mcp for equities, crypto and prediction markets in one place.
Scored across 11 tools
Most tools are clearly separable: discovery (search/list_categories), schema inspection, quoting vs execution are all explained with explicit 'do this, not that' guidance. The main fuzziness comes from the composite twitter_stock_pulse overlapping with get_twitter_tweet_advanced_search + get_financial_prices_snapshot + get_financial_news, though its description does route agents correctly. The lingering deprecated `use` alias next to batch_use is an avoidable confusion point.
There is a coherent batch_* family and a get_* family, but the server also exposes bare nouns and oddballs (`account`, `search`, `use`, `twitter_stock_pulse`), mixing bare-noun, verb_noun, and noun_phrase styles in one surface. Readable, but not a single predictable pattern.
Eleven tools is a sensible size for a gateway-plus-finance server: auth, discovery, schema, quote, execute, and a handful of domain tools. Slightly padded by a deprecated `use` entry, but not bloated.
The gateway lifecycle (auth → search → schema → quote → execute) is fully covered, and the domain tools span news, prices, and X search. The main gap is that the deprecated `use` tool is left in place rather than removed, and there is no explicit cancellation/multi-step session management beyond session_id reuse.
Who am I, what can I use, how much can I spend: the key, the account balance, the Go-to-Market wallet when one is active, and usage for today, 7 days and 30 days. Free; needs the Authorization header. Call it to verify a new connection or to explain a 402. ok is true only when the balance was read; otherwise each entry of errors says what to do in next_step.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. |
| 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 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not required to restate it. It adds genuine operational context: the batch_use prohibition, exact-name/prefix requirements, and session reuse semantics. It does not cover failure handling when names are invalid, keeping it below a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core action and size limit, and every sentence carries workflow value. The session_id sentence duplicates the schema's own parameter description, which is minor redundancy rather than bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only batch retrieval tool with an output schema, the description supplies the orchestration context an agent needs (source of names, next steps, session handling) without needing to explain return values. Nothing essential to correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema by constraining names to those returned by search and warning against a client prefix such as mcp__aisa__, which is not encoded in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Retrieve schemas for 1 to 20 exact tool names') and pins the source of those names to search. This clearly separates it from siblings like search (finds tools), batch_quote, and batch_use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly sequences the workflow: build arguments from successful schemas, then call batch_quote, and 'Do not call batch_use yet.' This is an explicit when-to-use and when-not-to-use instruction naming the alternative siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. |
| 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. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well past the readOnly/idempotent annotations by explaining that quotes are price observations rather than authorization grants, and precisely delimiting what auto_execute_eligible does and does not waive (user prohibition, narrower scope, tighter budget). It also guarantees no execution fallback, which is the key behavioral risk for this tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose is front-loaded and most sentences carry distinct rules (no fallback, eligibility limits, naming, session reuse). It is on the long side and the argument-shape constraint is stated twice in spirit, but little is truly wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value documentation isn't required, yet the description still flags the two response fields that matter for a downstream decision. Combined with session and naming guidance, an agent has everything needed to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
At 67% schema coverage the schema already documents each parameter, so the description earns credit only for added meaning: exact-name rules for 'tool', session_id reuse semantics, and the 1-to-20 argument-shape parallel with batch_use. It doesn't clarify search_id beyond what the schema states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Obtain AIsaServices cost quotes for 1 to 20 published tools') plus the crucial scope qualifier 'without executing them.' It is immediately distinguishable from the sibling batch_use, which executes rather than quotes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly names the parallel sibling ('Same input as batch_use') and draws the boundary ('Never falls back to execution'). It also gives operational conditions: use names exactly as search returns them, strip any mcp__aisa__ prefix, and reuse session_id from Search for the task.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. |
| 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. |
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.
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.
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.
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.
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.
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.
Get recent news articles for a specific company or the broad market. Pass a ticker for company-specific news, or omit the ticker for general market news.
Published reference price: $0.02 USD per successful request. Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | The maximum number of news articles to return (default: 5, max: 10). This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`. Provider reference (supplier schema): `{"default":5,"maximum":10,"type":"integer"}`. | |
| cursor | No | Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it. | |
| ticker | No | The ticker symbol of the company. Omit for broad market news. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the full safe-read profile (readOnly, idempotent, non-destructive, openWorld), so the safety bar is low. The description adds the dual-mode behavior, but says nothing about freshness/coverage window, rate limits, or result ordering; the pricing line is injected boilerplate rather than authored disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, capability first and operational detail second, with zero filler in the authored text. The second sentence partially restates the dual-mode idea from the first, a minor redundancy; the trailing pricing block is auto-injected and not the author's conciseness burden.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists and the input schema fully documents all three parameters including pagination semantics, so the description need not explain returns. It still omits any hint about how far back news goes or how results are ordered, a small gap for a news tool but not one that blocks correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already carries the meaning of limit, cursor, and ticker (including "Omit for broad market news"), making 3 the correct baseline. The description's ticker guidance duplicates rather than extends the schema, adding no new syntax or constraint detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("Get recent news articles") and immediately clarifies the two operating modes: ticker-specific news vs. broad market news. No sibling among the get_financial_* tools overlaps with news retrieval, so the agent can route to it unambiguously from the name and first sentence.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells the agent how to select between the two modes ("Pass a ticker for company-specific news, or omit the ticker for general market news"), which is the main decision point. It stops short of naming alternatives for adjacent questions (e.g., filings or earnings coverage), so no exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the real-time price snapshot for a stock, including the current price, day change, and day change percent.
Published reference price: $0.02 USD per successful request. Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | No | The stock ticker symbol (e.g. AAPL, MSFT). |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint, so the safety profile is covered. The description usefully adds that the data is real-time and lists the returned fields, but says nothing about pricing/auth behavior beyond the injected billing note or about latency/freshness guarantees.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core sentence is front-loaded, tight, and waste-free, leading with the operation and then the payload. The appended pricing block is injected boilerplate rather than authored content and mildly dilutes the signal.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 not be explained, and the description redundantly summarizes them anyway. However, the schema marks 'ticker' as optional (required list is empty) while the description implies a stock must be named, and no guidance resolves that ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with a single well-documented 'ticker' parameter, so the baseline is 3. The description adds no format, exchange-suffix, or casing guidance beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb and resource ('Get the real-time price snapshot for a stock') and enumerates the returned fields (current price, day change, day change percent). It implicitly distinguishes itself from the sibling get_financial_prices by emphasizing 'snapshot' and 'real-time', but does not name or contrast that sibling explicitly, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool versus get_financial_prices, get_financial_financial_metrics_snapshot, or the batch_quote/batch_use siblings. The word 'snapshot' hints at a lighter/faster alternative but the agent must infer that from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search X posts by keyword or query with X's advanced search operators, sorted by Latest (default) or Top. This is the primary entry point for X content research when you do not yet have tweet IDs or handles. Supports operators in the query string such as from:, to:, since:, until:, min_faves:, and -filter:replies. Cursor-paginated; returns tweets with has_next_page and next_cursor. To search accounts rather than posts use get_twitter_user_search. To read one account's own posts use get_twitter_user_tweet_timeline.
Usage-based billing; Default request estimate: $0.003 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| query | No | The query to search for. | |
| cursor | No | The cursor to paginate through the results. First page is empty. | |
| queryType | No | The query type to search for. Provider reference (supplier schema): `{"default":"Latest","enum":["Latest","Top"],"type":"string"}`. | |
| start_time | No | ||
| max_results | No |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the lower bar applies. The description still adds real behavior: cursor pagination semantics, the has_next_page/next_cursor return fields, sort modes, and supported query operators. It omits auth requirements and rate limits, which keeps it from a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with purpose, then operators, pagination, and alternatives in a tight sequence where each sentence carries information. The injected pricing boilerplate is not authored content but does add noise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 not be exhaustively explained, and annotations carry the safety profile. The description still covers usage context, alternatives, pagination flow, and query syntax, so nothing an agent needs to invoke it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%, so the schema does part of the work. The description usefully explains the query-string operator syntax and the Latest/Top sort (mapping to queryType), but count, max_results, and start_time are undocumented in both places. It adds value over the schema without fully compensating for the coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (search) and resource (X posts) and immediately differentiates itself by naming the two sibling alternatives for account search and user timelines. An agent can distinguish this from any account-scoped tool without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly declares when to use it ('primary entry point for X content research when you do not yet have tweet IDs or handles') and routes to the correct alternatives ('to search accounts use get_twitter_user_search', 'to read one account's posts use get_twitter_user_tweet_timeline'). Nothing is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The AIsa catalogue at a glance: categories, the servers in each, tool counts, and the dedicated endpoint to connect if you only need one category. Free. (AIsa-only: tool-router has no equivalent.) Use mcp.aisa.one/mcp?modules=<category> (or mcp.aisa.one/<category>/mcp) to have that category's tools listed directly instead of via search.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Discover AIsa tools and Plans for external data or actions. Skip tasks that only need supplied content or general knowledge. For multi-step tasks, search the full goal before decomposing it. Use English; put identifiers in known_fields. If has_full_schema=false, call batch_get_schema. Next call batch_quote, not batch_use. Do not search for standalone rewriting, translation, summarization, formatting, or calculations on supplied content. For one capability, use an atomic query. Select a matching capability, date window, and metric. A Plan may cover only part of the task; assess its purpose and follow next_steps_guidance.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of additional direct tool candidates. | |
| query | Yes | Natural-language capability or task to discover. | |
| category | No | Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.) | |
| 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. | |
| known_fields | No | Known values such as ticker, URL, provider, or identifier that improve retrieval. | |
| provider_filters | No | Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown. |
| Name | Required | Description |
|---|---|---|
| plan | No | |
| tools | Yes | |
| search_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. |
| retrieval_mode | No | |
| next_steps_guidance | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds workflow behavior the annotations cannot: the has_full_schema flag gates a required batch_get_schema call, and the next step after search is batch_quote, not batch_use. It stops short of disclosing retrieval limits or catalog breadth that would push it to a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a dense run of imperatives rather than flowing prose, but each sentence carries a distinct rule (scope, language, workflow branch, negative cases, result interpretation) and the most important scoping guidance is front-loaded. Slightly more compression would help.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 need not explain return values, and it correctly avoids doing so while still referencing the output fields that drive the workflow (has_full_schema, next_steps_guidance). A mutation-free, well-annotated search tool is adequately covered, though catalog scope ('AIsa-only', no external providers) could be stated more explicitly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the structured baseline is 3. The description adds genuine meaning beyond the schema by telling the agent to write the query in English and to place tickers, URLs, providers, or identifiers in known_fields, which is non-obvious routing guidance for a nested free-form object.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb+resource: 'Discover AIsa tools and Plans for external data or actions.' It also separates this discovery step from the sibling execution tools by naming batch_get_schema, batch_quote, and batch_use and stating when each follows, so an agent can place it in the workflow without opening schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit when-to-use ('tasks needing external data or actions'), when-not ('tasks that only need supplied content or general knowledge'; no standalone rewriting, translation, summarization, formatting, or calculations), and named alternatives (batch_get_schema when has_full_schema=false, batch_quote rather than batch_use). It also specifies query language and atomic-query style, 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.
Assemble everything behind "what is X saying about stocks right now" in one call.
Searches X/Twitter for a topic, extracts every $TICKER cashtag mentioned in the results, then fetches a price snapshot for the most-mentioned symbols — optionally recent company news too.
Use this when you need the posts AND the market data behind them together. Doing it yourself means one search call, parsing cashtags, then one price call per symbol, then joining the results; this returns the joined bundle.
Returns the raw tweets, per-symbol mention counts, price snapshots, a coverage
block saying which upstream sources succeeded or failed, and a billing block with
the calls made.
It does NOT rank, score, or interpret. mentions is a raw count, not a heat ranking —
you decide what "hot" means and what the numbers imply. If you only need the posts,
use get_twitter_tweet_advanced_search. If you already know the symbols, use
get_financial_prices_snapshot directly.
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | 7d | |
| topic | Yes | ||
| max_tickers | No | ||
| include_news | No |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it returns raw tweets, mention counts, price snapshots, a coverage block for upstream failures, and a billing block. It also explicitly states the tool does NOT rank or interpret, which prevents misuse. Minor gap: no mention of rate limits or pagination, but the coverage/billing disclosure is strong.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured and front-loaded with the core value proposition. It uses short paragraphs and bullet-like lists to convey the workflow, return contents, and exclusions. Every sentence earns its place, and the explicit 'does NOT' clarification prevents misinterpretation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has an output schema, so return values are documented elsewhere. The description covers the workflow, the joined data, the coverage/billing blocks, and the non-interpretation caveat. It lacks explicit mention of pagination or rate limits, but for a read-only aggregation tool with an output schema, this is nearly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It explains the overall flow (topic → cashtags → prices) and mentions 'most-mentioned symbols' which maps to max_tickers, and 'optionally recent company news' which maps to include_news. However, it does not explain the format of `since` (e.g., '7d' default) or the exact semantics of max_tickers beyond 'most-mentioned'. The description adds meaning but leaves some parameter details to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: it searches X/Twitter for a topic, extracts $TICKER cashtags, fetches price snapshots, and optionally news, then returns a joined bundle. It distinguishes itself from siblings by explicitly naming alternatives like get_twitter_tweet_advanced_search and get_financial_prices_snapshot.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool ('when you need the posts AND the market data behind them together') and when not to use it, naming the alternatives for posts-only or known-symbols cases. It also explains the manual multi-step alternative, making the tradeoff clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
deprecated, use batch_use instead
| Name | Required | Description | Default |
|---|---|---|---|
| arguments | No | Arguments matching input_schema / arguments_schema | |
| search_id | No | search_id from the search that found this operation | |
| operation_id | Yes | operation_id as returned by search | |
| max_price_usd | No | Refuse the call before any spend if its quoted price is above this many USD |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the agent knows this is a state-changing, open-world operation. The description adds only the deprecation status and says nothing about what gets mutated, spend behavior (despite a max_price_usd param), or authorization needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single clause with zero waste; the deprecation notice and the replacement are front-loaded. It is terse by design for a deprecated endpoint, though it is under-specified rather than optimally efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Has an output schema and annotations, which reduces the burden, but a 4-parameter operation tool with a deprecation notice gives no information about what it executes or whether it remains functional. For an agent deciding between this and batch_use, the description is thin.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all four parameters (operation_id, arguments, search_id, max_price_usd) are already documented in the schema. The description adds no parameter meaning on top, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description never states what the tool does — no verb or resource. It only labels the tool as deprecated and points to a replacement, leaving the actual capability ('Run an AIsa operation' from the title) unexplained. An agent must infer the purpose from the title and schema alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly routes the agent to the alternative ('use batch_use instead'), which is exactly the guidance needed for a deprecated tool. It doesn't explain when, if ever, this tool should still be called (e.g., during a migration window), so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
accountget_detailsget_financial_news3 fields changedInput schema / properties / cursorAdded value: +{
+ "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
+ "type": "string"
+}Input schema / properties / limit / descriptionAdded value: +"The maximum number of news articles to return (default: 5, max: 10). This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.\n\nProvider reference (supplier schema): `{\"default\":5,\"maximum\":10,\"type\":\"integer\"}`."Input schema / properties / ticker / descriptionAdded value: +"The ticker symbol of the company. Omit for broad market news."get_financial_prices_snapshot1 field changedInput schema / properties / ticker / descriptionAdded value: +"The stock ticker symbol (e.g. AAPL, MSFT)."get_twitter_tweet_advanced_search3 fields changedInput schema / properties / cursor / descriptionAdded value: +"The cursor to paginate through the results. First page is empty."Input schema / properties / query / descriptionAdded value: +"The query to search for."Input schema / properties / queryType / descriptionAdded value: +"The query type to search for.\n\nProvider reference (supplier schema): `{\"default\":\"Latest\",\"enum\":[\"Latest\",\"Top\"],\"type\":\"string\"}`."batch_get_schemabatch_quotebatch_use18 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / descriptionRemoved value: -"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch"Input schema / properties / calls / items / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / items / additionalPropertiesPrevious value: -trueNew value: +falseInput schema / properties / calls / items / propertiesAdded 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"
+ }
+}Input schema / properties / calls / items / requiredAdded value: +[
+ "call_id",
+ "tool",
+ "arguments"
+]Input schema / properties / calls / maxItemsAdded value: +20Input schema / properties / calls / minItemsAdded value: +1Input schema / properties / max_price_usdRemoved value: -{
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Per-call price cap applied to every item"
-}Input schema / properties / search_id / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / search_id / defaultRemoved value: -nullInput schema / properties / search_id / descriptionPrevious value: -"search_id from the search that found these operations"New value: +"Optional search correlation identifier returned by search."Input schema / properties / search_id / typeAdded value: +"string"Input schema / properties / session_idAdded 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"
+}Output schema / $defsAdded 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."
+ }
+}Output schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Output schema / propertiesAdded 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"
+ }
+}Output schema / requiredAdded value: +[
+ "session_id",
+ "batch_id",
+ "total_count",
+ "success_count",
+ "error_count",
+ "results",
+ "next_steps_guidance"
+]get_details13 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / argumentsRemoved value: -{
- "anyOf": [
- {
- "additionalProperties": true,
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "The arguments the operation would be called with, for a price that reflects them. Keyed by operation_id for a batch, or passed flat for a single operation_id. Routes whose required parameters are validated before pricing have no price without them."
-}Input schema / properties / include_arguments_schemaAdded value: +{
+ "default": true,
+ "description": "Return the complete arguments_schema. Defaults to true.",
+ "type": "boolean"
+}Input schema / properties / include_documentation / descriptionPrevious value: -"Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged."New value: +"Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support."Input schema / properties / include_response_schemaAdded value: +{
+ "default": false,
+ "description": "Return the complete response_schema. Defaults to false.",
+ "type": "boolean"
+}Input schema / properties / operation_idRemoved value: -{
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "One operation_id from search"
-}Input schema / properties / operation_idsRemoved value: -{
- "anyOf": [
- {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Up to 20 operation_ids, for a batch"
-}Input schema / properties / session_idAdded 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"
+}Input schema / properties / toolsAdded value: +{
+ "description": "Exact tool names returned by search whose complete contracts are needed. Never invent tool names.",
+ "items": {
+ "minLength": 1,
+ "pattern": "^\\S(?:.*\\S)?$",
+ "type": "string"
+ },
+ "maxItems": 20,
+ "minItems": 1,
+ "type": "array",
+ "uniqueItems": true
+}Input schema / properties / with_quoteRemoved value: -{
- "default": true,
- "description": "Whether each operation is priced for this account before the answer. One round trip per operation; spends nothing.",
- "type": "boolean"
-}Input schema / requiredAdded value: +[
+ "tools"
+]Output schema / propertiesAdded value: +{
+ "error_count": {
+ "type": "integer"
+ },
+ "next_steps_guidance": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "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_-]{1,128}$",
+ "type": "string"
+ },
+ "success_count": {
+ "type": "integer"
+ },
+ "tools": {
+ "additionalProperties": {
+ "additionalProperties": false,
+ "properties": {
+ "arguments_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "canonical_operation_id": {
+ "type": "string"
+ },
+ "documentation": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "error": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ]
+ },
+ "execution_supported": {
+ "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
+ "type": "boolean"
+ },
+ "execution_unsupported_reason": {
+ "description": "Why execution and quoting remain unavailable through this router.",
+ "type": "string"
+ },
+ "idempotent": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "boolean"
+ }
+ ]
+ },
+ "known_pitfalls": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "read_only": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "boolean"
+ }
+ ]
+ },
+ "response_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "side_effects": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "successful": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "successful"
+ ],
+ "type": "object"
+ },
+ "type": "object"
+ },
+ "total_count": {
+ "type": "integer"
+ }
+}Output schema / requiredAdded value: +[
+ "error_count",
+ "next_steps_guidance",
+ "session_id",
+ "success_count",
+ "tools",
+ "total_count"
+]get_financial_news5 fields changedInput schema / properties / limit / defaultRemoved value: -5Input schema / properties / limit / descriptionRemoved value: -"The maximum number of news articles to return (default: 5, max: 10)."Input schema / properties / limit / maximumRemoved value: -10Input schema / properties / limit / typePrevious value: -"integer"New value: +"string"Input schema / properties / ticker / descriptionRemoved value: -"The ticker symbol of the company. Omit for broad market news."get_financial_prices_snapshot2 fields changedInput schema / properties / ticker / descriptionRemoved value: -"The stock ticker symbol (e.g. AAPL, MSFT)."Input schema / requiredPrevious value: -[
- "ticker"
-]New value: +[]get_twitter_tweet_advanced_search9 fields changedInput schema / properties / countAdded value: +{
+ "type": "string"
+}Input schema / properties / cursor / descriptionRemoved value: -"The cursor to paginate through the results. First page is empty."Input schema / properties / max_resultsAdded value: +{
+ "type": "string"
+}Input schema / properties / query / descriptionRemoved value: -"The query to search for."Input schema / properties / queryType / defaultRemoved value: -"Latest"Input schema / properties / queryType / descriptionRemoved value: -"The query type to search for."Input schema / properties / queryType / enumRemoved value: -[
- "Latest",
- "Top"
-]Input schema / properties / start_timeAdded value: +{
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "query",
- "queryType"
-]New value: +[]search17 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / category / anyOfRemoved value: -[
- {
- "enum": [
- "seo",
- "finance",
- "social",
- "search",
- "sales",
- "mail"
- ],
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / category / defaultRemoved value: -nullInput schema / properties / category / descriptionPrevious value: -"Restrict to one category (seo, finance, social, search, sales, mail). Omit to search everything."New value: +"Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.)"Input schema / properties / category / enumAdded value: +[
+ "seo",
+ "finance",
+ "social",
+ "search",
+ "sales",
+ "mail"
+]Input schema / properties / category / typeAdded value: +"string"Input schema / properties / known_fieldsAdded value: +{
+ "additionalProperties": true,
+ "default": {},
+ "description": "Known values such as ticker, URL, provider, or identifier that improve retrieval.",
+ "type": "object"
+}Input schema / properties / limit / descriptionPrevious value: -"Maximum candidates, 1-10"New value: +"Maximum number of additional direct tool candidates."Input schema / properties / limit / maximumAdded value: +20Input schema / properties / limit / minimumAdded value: +1Input schema / properties / provider_filtersAdded value: +{
+ "default": [],
+ "description": "Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown.",
+ "items": {
+ "type": "string"
+ },
+ "maxItems": 50,
+ "type": "array",
+ "uniqueItems": true
+}Input schema / properties / query / descriptionPrevious value: -"What you need, in plain language, e.g. 'backlinks of a domain', 'recent tweets by a user', 'insider trades for AAPL'. English works best."New value: +"Natural-language capability or task to discover."Input schema / properties / query / maxLengthAdded value: +2000Input schema / properties / query / minLengthAdded value: +1Input schema / properties / session_idAdded 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"
+}Output schema / propertiesAdded value: +{
+ "next_steps_guidance": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "plan": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "canonical_use_case": {
+ "type": "string"
+ },
+ "description": {
+ "type": "string"
+ },
+ "known_pitfalls": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "plan_ref": {
+ "type": "string"
+ },
+ "primary_tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "recommended_steps": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "related_tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ },
+ "required": [
+ "canonical_use_case",
+ "description",
+ "known_pitfalls",
+ "plan_ref",
+ "primary_tools",
+ "recommended_steps",
+ "related_tools"
+ ]
+ },
+ "retrieval_mode": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "string"
+ }
+ ]
+ },
+ "search_id": {
+ "type": "string"
+ },
+ "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_-]{1,128}$",
+ "type": "string"
+ },
+ "tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "arguments_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "description": {
+ "type": "string"
+ },
+ "execution_supported": {
+ "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
+ "type": "boolean"
+ },
+ "execution_unsupported_reason": {
+ "description": "Why execution and quoting remain unavailable through this router.",
+ "type": "string"
+ },
+ "has_full_schema": {
+ "type": "boolean"
+ },
+ "match_reasons": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "price": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "retrieval_debug": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "fused_rank": {
+ "type": "integer"
+ },
+ "fused_score": {
+ "type": "number"
+ },
+ "lexical_rank": {
+ "type": "integer"
+ },
+ "lexical_score": {
+ "type": "number"
+ },
+ "rerank_admission_rank": {
+ "type": "integer"
+ },
+ "rerank_rank": {
+ "type": "integer"
+ },
+ "rerank_score": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "number"
+ }
+ ]
+ },
+ "runtime_availability": {
+ "type": "string"
+ },
+ "vector_view_ranks": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "vector_view_scores": {
+ "additionalProperties": {
+ "type": "number"
+ },
+ "type": "object"
+ }
+ },
+ "required": [
+ "fused_rank",
+ "fused_score",
+ "lexical_rank",
+ "lexical_score",
+ "rerank_admission_rank",
+ "rerank_rank",
+ "runtime_availability",
+ "vector_view_ranks",
+ "vector_view_scores"
+ ]
+ },
+ "summary": {
+ "type": "string"
+ },
+ "tool": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "description",
+ "has_full_schema",
+ "price",
+ "summary",
+ "tool"
+ ],
+ "type": "object"
+ }
+ }
+}Output schema / requiredAdded value: +[
+ "next_steps_guidance",
+ "search_id",
+ "session_id",
+ "tools"
+]use1 field changedInput schema / properties / max_price_usd / descriptionPrevious value: -"Refuse the call before any spend if it would cost more than this many USD"New value: +"Refuse the call before any spend if its quoted price is above this many USD"batch_get_schemabatch_quotebatch_use18 fields changedInput schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / descriptionAdded value: +"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch"Input schema / properties / calls / items / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / items / additionalPropertiesPrevious value: -falseNew value: +trueInput schema / properties / calls / items / propertiesRemoved 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"
- }
-}Input schema / properties / calls / items / requiredRemoved value: -[
- "call_id",
- "tool",
- "arguments"
-]Input schema / properties / calls / maxItemsRemoved value: -20Input schema / properties / calls / minItemsRemoved value: -1Input schema / properties / max_price_usdAdded value: +{
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Per-call price cap applied to every item"
+}Input schema / properties / search_id / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / search_id / defaultAdded value: +nullInput schema / properties / search_id / descriptionPrevious value: -"Optional search correlation identifier returned by search."New value: +"search_id from the search that found these operations"Input schema / properties / search_id / typeRemoved value: -"string"Input schema / properties / session_idRemoved 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"
-}Output schema / $defsRemoved 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."
- }
-}Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / propertiesRemoved 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"
- }
-}Output schema / requiredRemoved value: -[
- "session_id",
- "batch_id",
- "total_count",
- "success_count",
- "error_count",
- "results",
- "next_steps_guidance"
-]get_details13 fields changedInput schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / argumentsAdded value: +{
+ "anyOf": [
+ {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "The arguments the operation would be called with, for a price that reflects them. Keyed by operation_id for a batch, or passed flat for a single operation_id. Routes whose required parameters are validated before pricing have no price without them."
+}Input schema / properties / include_arguments_schemaRemoved value: -{
- "default": true,
- "description": "Return the complete arguments_schema. Defaults to true.",
- "type": "boolean"
-}Input schema / properties / include_documentation / descriptionPrevious value: -"Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support."New value: +"Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged."Input schema / properties / include_response_schemaRemoved value: -{
- "default": false,
- "description": "Return the complete response_schema. Defaults to false.",
- "type": "boolean"
-}Input schema / properties / operation_idAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "One operation_id from search"
+}Input schema / properties / operation_idsAdded value: +{
+ "anyOf": [
+ {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Up to 20 operation_ids, for a batch"
+}Input schema / properties / session_idRemoved 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"
-}Input schema / properties / toolsRemoved value: -{
- "description": "Exact tool names returned by search whose complete contracts are needed. Never invent tool names.",
- "items": {
- "minLength": 1,
- "pattern": "^\\S(?:.*\\S)?$",
- "type": "string"
- },
- "maxItems": 20,
- "minItems": 1,
- "type": "array",
- "uniqueItems": true
-}Input schema / properties / with_quoteAdded value: +{
+ "default": true,
+ "description": "Whether each operation is priced for this account before the answer. One round trip per operation; spends nothing.",
+ "type": "boolean"
+}Input schema / requiredRemoved value: -[
- "tools"
-]Output schema / propertiesRemoved value: -{
- "error_count": {
- "type": "integer"
- },
- "next_steps_guidance": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "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_-]{1,128}$",
- "type": "string"
- },
- "success_count": {
- "type": "integer"
- },
- "tools": {
- "additionalProperties": {
- "additionalProperties": false,
- "properties": {
- "arguments_schema": {
- "additionalProperties": true,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ]
- },
- "canonical_operation_id": {
- "type": "string"
- },
- "documentation": {
- "additionalProperties": true,
- "type": "object"
- },
- "error": {
- "additionalProperties": false,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ],
- "properties": {
- "code": {
- "type": "string"
- },
- "message": {
- "type": "string"
- }
- },
- "required": [
- "code",
- "message"
- ]
- },
- "execution_supported": {
- "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
- "type": "boolean"
- },
- "execution_unsupported_reason": {
- "description": "Why execution and quoting remain unavailable through this router.",
- "type": "string"
- },
- "idempotent": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "boolean"
- }
- ]
- },
- "known_pitfalls": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "read_only": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "boolean"
- }
- ]
- },
- "response_schema": {
- "additionalProperties": true,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ]
- },
- "side_effects": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "successful": {
- "type": "boolean"
- }
- },
- "required": [
- "successful"
- ],
- "type": "object"
- },
- "type": "object"
- },
- "total_count": {
- "type": "integer"
- }
-}Output schema / requiredRemoved value: -[
- "error_count",
- "next_steps_guidance",
- "session_id",
- "success_count",
- "tools",
- "total_count"
-]get_financial_news5 fields changedInput schema / properties / limit / defaultAdded value: +5Input schema / properties / limit / descriptionAdded value: +"The maximum number of news articles to return (default: 5, max: 10)."Input schema / properties / limit / maximumAdded value: +10Input schema / properties / limit / typePrevious value: -"string"New value: +"integer"Input schema / properties / ticker / descriptionAdded value: +"The ticker symbol of the company. Omit for broad market news."get_financial_prices_snapshot2 fields changedInput schema / properties / ticker / descriptionAdded value: +"The stock ticker symbol (e.g. AAPL, MSFT)."Input schema / requiredPrevious value: -[]New value: +[
+ "ticker"
+]get_twitter_tweet_advanced_search9 fields changedInput schema / properties / countRemoved value: -{
- "type": "string"
-}Input schema / properties / cursor / descriptionAdded value: +"The cursor to paginate through the results. First page is empty."Input schema / properties / max_resultsRemoved value: -{
- "type": "string"
-}Input schema / properties / query / descriptionAdded value: +"The query to search for."Input schema / properties / queryType / defaultAdded value: +"Latest"Input schema / properties / queryType / descriptionAdded value: +"The query type to search for."Input schema / properties / queryType / enumAdded value: +[
+ "Latest",
+ "Top"
+]Input schema / properties / start_timeRemoved value: -{
- "type": "string"
-}Input schema / requiredPrevious value: -[]New value: +[
+ "query",
+ "queryType"
+]search17 fields changedInput schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / category / anyOfAdded value: +[
+ {
+ "enum": [
+ "seo",
+ "finance",
+ "social",
+ "search",
+ "sales",
+ "mail"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / category / defaultAdded value: +nullInput schema / properties / category / descriptionPrevious value: -"Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.)"New value: +"Restrict to one category (seo, finance, social, search, sales, mail). Omit to search everything."Input schema / properties / category / enumRemoved value: -[
- "seo",
- "finance",
- "social",
- "search",
- "sales",
- "mail"
-]Input schema / properties / category / typeRemoved value: -"string"Input schema / properties / known_fieldsRemoved value: -{
- "additionalProperties": true,
- "default": {},
- "description": "Known values such as ticker, URL, provider, or identifier that improve retrieval.",
- "type": "object"
-}Input schema / properties / limit / descriptionPrevious value: -"Maximum number of additional direct tool candidates."New value: +"Maximum candidates, 1-10"Input schema / properties / limit / maximumRemoved value: -20Input schema / properties / limit / minimumRemoved value: -1Input schema / properties / provider_filtersRemoved value: -{
- "default": [],
- "description": "Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown.",
- "items": {
- "type": "string"
- },
- "maxItems": 50,
- "type": "array",
- "uniqueItems": true
-}Input schema / properties / query / descriptionPrevious value: -"Natural-language capability or task to discover."New value: +"What you need, in plain language, e.g. 'backlinks of a domain', 'recent tweets by a user', 'insider trades for AAPL'. English works best."Input schema / properties / query / maxLengthRemoved value: -2000Input schema / properties / query / minLengthRemoved value: -1Input schema / properties / session_idRemoved 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"
-}Output schema / propertiesRemoved value: -{
- "next_steps_guidance": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "plan": {
- "additionalProperties": false,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ],
- "properties": {
- "canonical_use_case": {
- "type": "string"
- },
- "description": {
- "type": "string"
- },
- "known_pitfalls": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "plan_ref": {
- "type": "string"
- },
- "primary_tools": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "recommended_steps": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "related_tools": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- }
- },
- "required": [
- "canonical_use_case",
- "description",
- "known_pitfalls",
- "plan_ref",
- "primary_tools",
- "recommended_steps",
- "related_tools"
- ]
- },
- "retrieval_mode": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "string"
- }
- ]
- },
- "search_id": {
- "type": "string"
- },
- "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_-]{1,128}$",
- "type": "string"
- },
- "tools": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "additionalProperties": false,
- "properties": {
- "arguments_schema": {
- "additionalProperties": true,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ]
- },
- "description": {
- "type": "string"
- },
- "execution_supported": {
- "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
- "type": "boolean"
- },
- "execution_unsupported_reason": {
- "description": "Why execution and quoting remain unavailable through this router.",
- "type": "string"
- },
- "has_full_schema": {
- "type": "boolean"
- },
- "match_reasons": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "price": {
- "additionalProperties": true,
- "type": "object"
- },
- "retrieval_debug": {
- "additionalProperties": false,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ],
- "properties": {
- "fused_rank": {
- "type": "integer"
- },
- "fused_score": {
- "type": "number"
- },
- "lexical_rank": {
- "type": "integer"
- },
- "lexical_score": {
- "type": "number"
- },
- "rerank_admission_rank": {
- "type": "integer"
- },
- "rerank_rank": {
- "type": "integer"
- },
- "rerank_score": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "number"
- }
- ]
- },
- "runtime_availability": {
- "type": "string"
- },
- "vector_view_ranks": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "vector_view_scores": {
- "additionalProperties": {
- "type": "number"
- },
- "type": "object"
- }
- },
- "required": [
- "fused_rank",
- "fused_score",
- "lexical_rank",
- "lexical_score",
- "rerank_admission_rank",
- "rerank_rank",
- "runtime_availability",
- "vector_view_ranks",
- "vector_view_scores"
- ]
- },
- "summary": {
- "type": "string"
- },
- "tool": {
- "type": "string"
- }
- },
- "required": [
- "description",
- "has_full_schema",
- "price",
- "summary",
- "tool"
- ],
- "type": "object"
- }
- }
-}Output schema / requiredRemoved value: -[
- "next_steps_guidance",
- "search_id",
- "session_id",
- "tools"
-]use1 field changedInput schema / properties / max_price_usd / descriptionPrevious value: -"Refuse the call before any spend if its quoted price is above this many USD"New value: +"Refuse the call before any spend if it would cost more than this many USD"batch_get_schemabatch_quotebatch_use18 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / descriptionRemoved value: -"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch"Input schema / properties / calls / items / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / items / additionalPropertiesPrevious value: -trueNew value: +falseInput schema / properties / calls / items / propertiesAdded 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"
+ }
+}Input schema / properties / calls / items / requiredAdded value: +[
+ "call_id",
+ "tool",
+ "arguments"
+]Input schema / properties / calls / maxItemsAdded value: +20Input schema / properties / calls / minItemsAdded value: +1Input schema / properties / max_price_usdRemoved value: -{
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Per-call price cap applied to every item"
-}Input schema / properties / search_id / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / search_id / defaultRemoved value: -nullInput schema / properties / search_id / descriptionPrevious value: -"search_id from the search that found these operations"New value: +"Optional search correlation identifier returned by search."Input schema / properties / search_id / typeAdded value: +"string"Input schema / properties / session_idAdded 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"
+}Output schema / $defsAdded 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."
+ }
+}Output schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Output schema / propertiesAdded 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"
+ }
+}Output schema / requiredAdded value: +[
+ "session_id",
+ "batch_id",
+ "total_count",
+ "success_count",
+ "error_count",
+ "results",
+ "next_steps_guidance"
+]get_details13 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / argumentsRemoved value: -{
- "anyOf": [
- {
- "additionalProperties": true,
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "The arguments the operation would be called with, for a price that reflects them. Keyed by operation_id for a batch, or passed flat for a single operation_id. Routes whose required parameters are validated before pricing have no price without them."
-}Input schema / properties / include_arguments_schemaAdded value: +{
+ "default": true,
+ "description": "Return the complete arguments_schema. Defaults to true.",
+ "type": "boolean"
+}Input schema / properties / include_documentation / descriptionPrevious value: -"Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged."New value: +"Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support."Input schema / properties / include_response_schemaAdded value: +{
+ "default": false,
+ "description": "Return the complete response_schema. Defaults to false.",
+ "type": "boolean"
+}Input schema / properties / operation_idRemoved value: -{
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "One operation_id from search"
-}Input schema / properties / operation_idsRemoved value: -{
- "anyOf": [
- {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Up to 20 operation_ids, for a batch"
-}Input schema / properties / session_idAdded 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"
+}Input schema / properties / toolsAdded value: +{
+ "description": "Exact tool names returned by search whose complete contracts are needed. Never invent tool names.",
+ "items": {
+ "minLength": 1,
+ "pattern": "^\\S(?:.*\\S)?$",
+ "type": "string"
+ },
+ "maxItems": 20,
+ "minItems": 1,
+ "type": "array",
+ "uniqueItems": true
+}Input schema / properties / with_quoteRemoved value: -{
- "default": true,
- "description": "Whether each operation is priced for this account before the answer. One round trip per operation; spends nothing.",
- "type": "boolean"
-}Input schema / requiredAdded value: +[
+ "tools"
+]Output schema / propertiesAdded value: +{
+ "error_count": {
+ "type": "integer"
+ },
+ "next_steps_guidance": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "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_-]{1,128}$",
+ "type": "string"
+ },
+ "success_count": {
+ "type": "integer"
+ },
+ "tools": {
+ "additionalProperties": {
+ "additionalProperties": false,
+ "properties": {
+ "arguments_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "canonical_operation_id": {
+ "type": "string"
+ },
+ "documentation": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "error": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ]
+ },
+ "execution_supported": {
+ "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
+ "type": "boolean"
+ },
+ "execution_unsupported_reason": {
+ "description": "Why execution and quoting remain unavailable through this router.",
+ "type": "string"
+ },
+ "idempotent": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "boolean"
+ }
+ ]
+ },
+ "known_pitfalls": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "read_only": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "boolean"
+ }
+ ]
+ },
+ "response_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "side_effects": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "successful": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "successful"
+ ],
+ "type": "object"
+ },
+ "type": "object"
+ },
+ "total_count": {
+ "type": "integer"
+ }
+}Output schema / requiredAdded value: +[
+ "error_count",
+ "next_steps_guidance",
+ "session_id",
+ "success_count",
+ "tools",
+ "total_count"
+]get_financial_news5 fields changedInput schema / properties / limit / defaultRemoved value: -5Input schema / properties / limit / descriptionRemoved value: -"The maximum number of news articles to return (default: 5, max: 10)."Input schema / properties / limit / maximumRemoved value: -10Input schema / properties / limit / typePrevious value: -"integer"New value: +"string"Input schema / properties / ticker / descriptionRemoved value: -"The ticker symbol of the company. Omit for broad market news."get_financial_prices_snapshot2 fields changedInput schema / properties / ticker / descriptionRemoved value: -"The stock ticker symbol (e.g. AAPL, MSFT)."Input schema / requiredPrevious value: -[
- "ticker"
-]New value: +[]get_twitter_tweet_advanced_search9 fields changedInput schema / properties / countAdded value: +{
+ "type": "string"
+}Input schema / properties / cursor / descriptionRemoved value: -"The cursor to paginate through the results. First page is empty."Input schema / properties / max_resultsAdded value: +{
+ "type": "string"
+}Input schema / properties / query / descriptionRemoved value: -"The query to search for."Input schema / properties / queryType / defaultRemoved value: -"Latest"Input schema / properties / queryType / descriptionRemoved value: -"The query type to search for."Input schema / properties / queryType / enumRemoved value: -[
- "Latest",
- "Top"
-]Input schema / properties / start_timeAdded value: +{
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "query",
- "queryType"
-]New value: +[]search17 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / category / anyOfRemoved value: -[
- {
- "enum": [
- "seo",
- "finance",
- "social",
- "search",
- "sales",
- "mail"
- ],
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / category / defaultRemoved value: -nullInput schema / properties / category / descriptionPrevious value: -"Restrict to one category (seo, finance, social, search, sales, mail). Omit to search everything."New value: +"Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.)"Input schema / properties / category / enumAdded value: +[
+ "seo",
+ "finance",
+ "social",
+ "search",
+ "sales",
+ "mail"
+]Input schema / properties / category / typeAdded value: +"string"Input schema / properties / known_fieldsAdded value: +{
+ "additionalProperties": true,
+ "default": {},
+ "description": "Known values such as ticker, URL, provider, or identifier that improve retrieval.",
+ "type": "object"
+}Input schema / properties / limit / descriptionPrevious value: -"Maximum candidates, 1-10"New value: +"Maximum number of additional direct tool candidates."Input schema / properties / limit / maximumAdded value: +20Input schema / properties / limit / minimumAdded value: +1Input schema / properties / provider_filtersAdded value: +{
+ "default": [],
+ "description": "Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown.",
+ "items": {
+ "type": "string"
+ },
+ "maxItems": 50,
+ "type": "array",
+ "uniqueItems": true
+}Input schema / properties / query / descriptionPrevious value: -"What you need, in plain language, e.g. 'backlinks of a domain', 'recent tweets by a user', 'insider trades for AAPL'. English works best."New value: +"Natural-language capability or task to discover."Input schema / properties / query / maxLengthAdded value: +2000Input schema / properties / query / minLengthAdded value: +1Input schema / properties / session_idAdded 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"
+}Output schema / propertiesAdded value: +{
+ "next_steps_guidance": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "plan": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "canonical_use_case": {
+ "type": "string"
+ },
+ "description": {
+ "type": "string"
+ },
+ "known_pitfalls": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "plan_ref": {
+ "type": "string"
+ },
+ "primary_tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "recommended_steps": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "related_tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ },
+ "required": [
+ "canonical_use_case",
+ "description",
+ "known_pitfalls",
+ "plan_ref",
+ "primary_tools",
+ "recommended_steps",
+ "related_tools"
+ ]
+ },
+ "retrieval_mode": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "string"
+ }
+ ]
+ },
+ "search_id": {
+ "type": "string"
+ },
+ "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_-]{1,128}$",
+ "type": "string"
+ },
+ "tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "arguments_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "description": {
+ "type": "string"
+ },
+ "execution_supported": {
+ "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
+ "type": "boolean"
+ },
+ "execution_unsupported_reason": {
+ "description": "Why execution and quoting remain unavailable through this router.",
+ "type": "string"
+ },
+ "has_full_schema": {
+ "type": "boolean"
+ },
+ "match_reasons": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "price": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "retrieval_debug": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "fused_rank": {
+ "type": "integer"
+ },
+ "fused_score": {
+ "type": "number"
+ },
+ "lexical_rank": {
+ "type": "integer"
+ },
+ "lexical_score": {
+ "type": "number"
+ },
+ "rerank_admission_rank": {
+ "type": "integer"
+ },
+ "rerank_rank": {
+ "type": "integer"
+ },
+ "rerank_score": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "number"
+ }
+ ]
+ },
+ "runtime_availability": {
+ "type": "string"
+ },
+ "vector_view_ranks": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "vector_view_scores": {
+ "additionalProperties": {
+ "type": "number"
+ },
+ "type": "object"
+ }
+ },
+ "required": [
+ "fused_rank",
+ "fused_score",
+ "lexical_rank",
+ "lexical_score",
+ "rerank_admission_rank",
+ "rerank_rank",
+ "runtime_availability",
+ "vector_view_ranks",
+ "vector_view_scores"
+ ]
+ },
+ "summary": {
+ "type": "string"
+ },
+ "tool": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "description",
+ "has_full_schema",
+ "price",
+ "summary",
+ "tool"
+ ],
+ "type": "object"
+ }
+ }
+}Output schema / requiredAdded value: +[
+ "next_steps_guidance",
+ "search_id",
+ "session_id",
+ "tools"
+]use1 field changedInput schema / properties / max_price_usd / descriptionPrevious value: -"Refuse the call before any spend if it would cost more than this many USD"New value: +"Refuse the call before any spend if its quoted price is above this many USD"get_details1 field changedInput schema / properties / include_documentationAdded value: +{
+ "default": false,
+ "description": "Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged.",
+ "type": "boolean"
+}batch_useget_detailsget_financial_newsget_financial_prices_snapshotget_twitter_tweet_advanced_searchlist_categoriessearchtwitter_stock_pulseuseYour agent needs markets — prices and fundamentals for listed companies, the filings behind them, crypto, and what the prediction markets put the odds at. **What you can ask for** • "Pull this company's income statement, cash flow and balance sheet for the last 8 quarters." • "What did insiders buy or sell, and when?" • "Snapshot prices for these 50 tickers, then the OHLC history for the three that moved." • "What are the current odds on this event across Kalshi and Polymarket?" • "Screen for companies matching these financial criteria." **How to use it** Point any MCP client at https://mcp.aisa.one/finance/mcp and sign in with OAuth — there is no key to create or paste. 49 tools: prices and snapshots, income statements, balance sheets and cash flows, metrics and ratios, earnings and analyst estimates, filings and line-item search, insider trades, macro interest rates, news, a screener; CoinGecko spot prices, market tables, OHLC, per-venue tickers and trending; Kalshi and Polymarket markets and trades; plus EDINET filings for Japan. **Why this rather than the source** Equities, crypto and event markets behind one account, so a cross-asset question is one conversation. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Read the number here, then ask the same agent what X is saying about the ticker today — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/marketpulse/mcp · /crypto-market-data/mcp · /prediction-market-data/mcp · /stock-pulse/mcp for one slice each.
Your agent needs company financials it can compute on — statements, ratios, earnings, estimates, filings and insider activity as structured data, not a PDF. **What you can ask for** • "Give me 8 quarters of income statement, balance sheet and cash flow for this ticker." • "What do analysts estimate for next quarter, and how did the last four surprise?" • "Find this exact line item across every filing." • "Who bought or sold as an insider in the last 90 days?" • "Screen for profitable companies under this valuation with growing revenue." **How to use it** Point any MCP client at https://mcp.aisa.one/marketpulse/mcp and sign in with OAuth — there is no key to create or paste. 21 tools: prices and snapshots, income statements, balance sheets, cash-flow statements, financial metrics and snapshots, earnings, analyst estimates, company facts, filings and filing items, line-item search, a screener, insider trades, macro interest rates, news, plus EDINET documents and filing digests for Japanese issuers. **Why this rather than the source** Statements as fields you can compute on, and a screener in the same place. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Read the fundamentals here, then ask the same agent what social is saying about the ticker — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/finance/mcp for equities, crypto and prediction markets in one place.
Your agent needs X/Twitter data — who follows a competitor, what a community is posting, who quoted that tweet, what is trending in Japan. Normally that means applying for an X developer account, passing app review, and managing a quota per endpoint. **What you can ask for** • "Who follows @stripe, and which of them are verified?" • "Pull every reply and quote on this tweet and summarise what people object to." • "List this community's moderators and its posts this week." • "What is trending in Japan right now?" • "Give me the full thread context behind this link, including the long-form article." **How to use it** Point any MCP client at https://mcp.aisa.one/twitter-api/mcp and sign in with OAuth — there is no key to create or paste. 29 read tools: users (profile, about, batch lookup by id, search, followers, verified followers, followings, follow check), tweets (timeline, latest, mentions, advanced search, replies, quotes, retweeters, thread context, articles), communities, lists, Spaces and trends. **Why this rather than the source** No developer account to apply for, no app review, no per-endpoint quota to manage. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Ask for a handle's followers here, then ask the same agent for that brand's search traffic, its backlinks, or the people to contact — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/social/mcp for X plus Instagram, Reddit, Pinterest and YouTube; https://mcp.aisa.one/gtm/mcp for those plus Similarweb and Apollo.
Your agent needs crypto prices it can rely on — spot, ranked market tables, history, OHLC, per-venue tickers, and what is trending right now. **What you can ask for** • "What is the price of these 20 tokens in USD and EUR right now?" • "Give me the top 100 by market cap with 24h and 7d change." • "Chart this coin's price over the last year, hourly." • "Where does this token trade, and at what spread per venue?" • "What is trending on CoinGecko today?" **How to use it** Point any MCP client at https://mcp.aisa.one/crypto-market-data/mcp and sign in with OAuth — there is no key to create or paste. 21 CoinGecko tools: simple price and token price by contract, supported currencies, coin list and detail, ranked markets, history, market charts and ranges, OHLC, per-coin tickers, categories, exchanges and their tickers, token data and charts, and trending. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Price the token here, then ask the same agent what X is posting about it — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/finance/mcp for equities, crypto and prediction markets in one place.
Add one secure layer between your agents and this server.
