"An explanation or exploration of reasoning" matching MCP tools:

• get_market_researchA

  skipseekA

  The written SkipSeek briefing for ONE market: what the pricing implies, what changed, the yes case and no case, catalysts and upcoming dates, resolution risk, an overall assessment with a confidence band and stated limitations — plus the source list behind it, with primary sources flagged. USE WHEN you need reasoning and citations rather than numbers, e.g. "why is this priced at 34%" or "what would move this". USE SOMETHING ELSE WHEN you only need the number (get_market_probabilities) or the trend (get_market_history). Read-only. Requires a SkipSeek API key — on the shared demo key it returns an explanation instead of content. Research is generated per market and published selectively, so a market with no published briefing returns an empty result, not an error.

  ConnectorNo auth

• open_negotiationA

  AgentMarketplaceA

  Open a negotiation on a bid — either the task's poster or the bid's bidder may start one, to adjust terms before the poster accepts. Creates the negotiation and immediately records `initial_terms` as its opening proposal (message_type "propose"), so it starts one round in. Use send_negotiation_message for every message after this one. Args: access_token: AgentAuth bearer token (requires ``market.post`` or ``market.bid``). bid_id: UUID of the bid to negotiate. initial_terms: JSONB — your opening proposal (e.g. revised cost or duration). reasoning: Optional free-text explanation for the proposal. Returns: ``{"negotiation": ..., "message": ...}`` on success. Errors: ``not_found``, ``authorization_failed`` (you're neither the task's poster nor the bid's bidder), ``invalid_input`` (missing initial_terms, bid not pending, or a negotiation is already active on this bid).

  ConnectorNo auth

• explain_scoreA

  yieldhunterA

  Agent-readable explanation of why an opportunity received its risk-adjusted score. Chain: pass list_yields opportunities[].id as poolId, opportunityId, or id (aliases for the same key). Returns a summary paragraph, factor bullets with weighted contributions, net-yield notes, and an exitRisk heuristic line (liquidity-only — not on-chain withdraw or transfer/eligibility; medium often confidence-driven, not pool size; extra bullet when knownIssues note transfer restrictions). sourceChainKey is ethereum|base|arbitrum only (unknown → VALIDATION_ERROR; no invented bridge fee). Prefer this when you need to justify a ranking to a human or another agent. Research only — non-custodial. Example: { "opportunityId": "43641cf5-a92e-416b-bce9-27113d3c0db6", "horizonDays": 30 } Also accepts poolId or id with the same value.

  ConnectorNo auth

• do_file_jobA

  ChangeThisFileA

  Describe what you want done to a file in plain language — e.g. "translate this contract to German", "pull every table out of this PDF into Excel", "shrink this video to under 25MB", "convert this to PDF". The instruction is routed to the right job automatically; if the request is not supported yet you get an honest explanation of what is. Provide EITHER source_url OR base64_content, plus a filename with extension.

  ConnectorNo auth

• explain_decisionA

  OneQAZ Trading IntelligenceA

  Purpose: Multi-layer explanation for a single symbol's recent research signal. Combines (1) technical score_trace from the signals store, (2) Thompson + regime scores from the virtual decision log (Thompson = Bayesian bandit sampling used for strategy selection), (3) news causality context. Use this when an AI must present a structured "why" rather than a raw verdict. Triggers (casual questions too): "why is BTC bullish?", "왜 이 종목이 매수야?", "explain that signal", "판단 근거 설명해줘", "walk me through the reasoning". When to call: when the user asks "why is this signal bullish/bearish?". Prerequisites: identify the symbol via get_signals or get_latest_decisions first. Next steps: none (this completes the explanation chain). Caveats: `symbol` must match the per-symbol signal store filename (lowercase). Output is research evidence, NOT a buy or sell recommendation.

  ConnectorNo auth

• explain_compliance_errorA

  ApierA

  Resolve a structured Apier compliance error code into a Norwegian-bokmål Explanation envelope: summary, bokmål why, ordered fix_steps, optional documentation link + legal_basis, and an optional handover block (who / where / what / why) for errors a human must resolve (e.g. AUTH_INSUFFICIENT_ROLE, AUTH_NO_DELEGATION, SCOPE_MISSING) — agent-resolvable errors ship `handover: null`. Accepts any code from the closed EXPLAINER_ERROR_CODES catalogue — pass whatever code an Apier endpoint returned in an error envelope. Optional flat context_org_number / context_scope / context_role / context_field / context_upstream_system strings carry placeholder values interpolated into the bokmål text; missing values fall back to 'ukjent <noun>'. Failure modes: VALIDATION_FAILED on an unknown code; SCOPE_INSUFFICIENT (needs read:rulebook). For a company's live obligations rather than an error explanation, use get_company_obligations instead. No API key? Bearer apier_sandbox_test_<suffix> (fresh suffix) serves synthetic fixtures; org numbers: GET /api/v1/sandbox/fixtures. Docs: https://www.apier.no/docs/guides/error-handling

  ConnectorNo auth

• memory_getA

  aziel-runtimeA

  Read one memory's stored explanation (node, history, or calibration: posterior, triad legs, effective N, Brier) — not a ranked list. Use this when you have a memory_id (or id) and need the stored explanation. Do not use it for ranked adaptive recall or appending an observation; use memory_recall or memory_observe instead. Missing both memory_id and id, or an unknown id, refuses AKM-NOT-FOUND — do not invent a node. authorizes_action stays false. There is no memory_delete; this is the read of the append-only node. Pass memory_id or id — one is enough; they are aliases, not two different records. Omit view for the default node slice. history returns events/resolutions; calibration returns posterior/triad/Brier. subject is not a lookup key here. Returns node, history, or calibration view (belief_is_not_truth).

  ConnectorNo auth

• chat_knowledgeA

  AlgoVault — Crypto Quant Trade CallsA

  Returns a synthesized natural-language answer with citations, grounded in the AlgoVault knowledge bundle (every MCP tool description, response shape, integration tutorial, and code example). Use when you need an explanation, code pattern, or how-to; for raw ranked snippets without LLM synthesis use search_knowledge (faster, no quota cost). Read-only: calls an LLM, no other side effects. Quota: Free 10/month, Starter 50, Pro 200, Enterprise 2000.

  ConnectorNo auth

• verify_integrityA

  RoomcommA

  Verify the cryptographic integrity of a room's message and revision chain. Checks Ed25519 signatures on messages, the hash-chain of claim revisions, and the arbiter's signatures. Use this before trusting a decision reached in a room you didn't monitor from the start. Returns {verdict: "CLEAN" | "REFUTED" | "INCONCLUSIVE", explanation, details}. Args: uuid: Room UUID or full room URL. Example: verify_integrity("a1b2…") before signing a handshake.

  ConnectorNo auth

• get_methodologyA

  life. scored.A

  Plain-English explanation of how scoring works, the two governing principles, what is deliberately left out (protected characteristics, luck), and the privacy stance. Use to answer "how does this work / is this fair" questions.

  ConnectorNo auth

• verify_integrityA

  roomcommA

  Verify the cryptographic integrity of a room's message and revision chain. Checks Ed25519 signatures on messages, the hash-chain of claim revisions, and the arbiter's signatures. Use this before trusting a decision reached in a room you didn't monitor from the start. Returns {verdict: "CLEAN" | "REFUTED" | "INCONCLUSIVE", explanation, details}. Args: uuid: Room UUID or full room URL. Example: verify_integrity("a1b2…") before signing a handshake.

  ConnectorNo auth

• legal_get_materialsA

  PRIMAMCPA

  Return the official legislative reasoning (Gesetzesbegründung / explanatory memorandum from a Bundestags-Drucksache) for a specific German federal provision — the source for genetic/historical interpretation: *what the legislator intended* with this norm. It answers questions that turn on a norm's purpose (ratio legis / 'why does this rule exist'), the meaning of an unclear or undefined term, whether a regulatory gap is planwidrig (grounds an analogy) or a deliberate silence (grounds an Umkehrschluss), or what a specific amendment was meant to achieve — the everyday uses of materials in an Auslegung or a Schriftsatz. Weight: the Begründung is strong evidence of legislative intent but not binding, and the statutory wording stays the outer limit of any reading. Pass a provision like '§ 823 BGB' or 'Art. 87a GG'. Returns the linked Begründungs-Abschnitte newest first, each with its 'BT-Drs.' Fundstelle, the reasoning text, and the other norms the same change amended ('target_norm_keys'). Complements ``legal_find_citing_decisions`` (how courts apply a norm) with the drafting intent behind it. Covers amendments since 1949 to German federal law (``gesetze-im-internet`` corpus) only; an unknown or non-German provision returns no materials. Excerpts are prepared from the Bundestag-extracted text, not the original PDF.

  ConnectorAPI key

• get_leadproof_replay_trialA

  LeadProof Sales AgentA

  Use specifically when a buyer wants to test duplicate-safe replay of failed lead deliveries before purchase. Returns the public replay procedure, fictional example audit, exact prerequisites, and attributed no-card production trial. For the standard trial without replay guidance, use get_leadproof_trial; for general exploration, use get_leadproof_evaluation_path.

  ConnectorNo auth

• send_negotiation_messageA

  AgentMarketplaceA

  Send the next message in an active negotiation. Args: access_token: AgentAuth bearer token (requires ``market.post`` or ``market.bid``). negotiation_id: UUID of the negotiation. message_type: One of ``counter``, ``accept``, ``reject``, ``clarify`` (``propose`` only ever happens once, via open_negotiation). proposed_terms: JSONB — required for ``counter``; becomes the new current terms on success. Ignored for accept/reject/clarify. reasoning: Optional free-text explanation. Returns: ``{"negotiation": ..., "message": ...}`` on success, plus ``{"assignment": {"task": ..., "bid": ...}}`` when this message is the ``accept`` that resolves the negotiation — accepting assigns the task to the bid's bidder in the same step (the task stays ``bidding`` throughout the negotiation and goes straight to ``assigned``), writing the agreed terms' cost and duration onto the bid. Errors: ``not_found``, ``authorization_failed`` (not a party to this negotiation), ``invalid_input`` (unknown message_type, negotiation not active, message not legal right now, max_rounds reached — accept or reject instead — or, on accept, the bid/task are no longer in an assignable state).

  ConnectorNo auth

• legal_get_materialsA

  PRIMAMCPA

  Return the official legislative reasoning (Gesetzesbegründung / explanatory memorandum from a Bundestags-Drucksache) for a specific German federal provision — the source for genetic/historical interpretation: *what the legislator intended* with this norm. It answers questions that turn on a norm's purpose (ratio legis / 'why does this rule exist'), the meaning of an unclear or undefined term, whether a regulatory gap is planwidrig (grounds an analogy) or a deliberate silence (grounds an Umkehrschluss), or what a specific amendment was meant to achieve — the everyday uses of materials in an Auslegung or a Schriftsatz. Weight: the Begründung is strong evidence of legislative intent but not binding, and the statutory wording stays the outer limit of any reading. Pass a provision like '§ 823 BGB' or 'Art. 87a GG'. Returns the linked Begründungs-Abschnitte newest first, each with its 'BT-Drs.' Fundstelle, the reasoning text, and the other norms the same change amended ('target_norm_keys'). Complements ``legal_find_citing_decisions`` (how courts apply a norm) with the drafting intent behind it. Covers amendments since 1949 to German federal law (``gesetze-im-internet`` corpus) only; an unknown or non-German provision returns no materials. Excerpts are prepared from the Bundestag-extracted text, not the original PDF.

  ConnectorAPI key

• get_dataforseo_ai_chat_gpt_llm_responses_modelsA

  AIsa AI VisibilityA

  The ChatGPT models available, each with `model_name`, `reasoning`, `web_search_supported` and `task_post_supported`. Measured at 5.2 KB, the largest of the four model lists. Free: upstream cost is 0. **Read it before calling** - an unlisted `model_name` is rejected with `status_code` 40501 inside an HTTP 200, and `task_post_supported` tells you whether the queued variant will work at all.

  ConnectorOAuth

• ceevee_explain_changeA

  CareerProof MCPA

  Get a detailed explanation of a specific edit from a positioning review (1 credit). The change_id comes from the edits array returned by ceevee_confirm_lens or ceevee_full_review. Returns a detailed rationale for the recommended change. cv_version_id from ceevee_upload_cv or ceevee_list_versions.

  ConnectorOAuth

• explainA

  flowpackA

  Natural-language explanation of a plan_id (what it does) or setting_path (what one setting controls). Audience: merchant (default), developer, or reviewer. Detail: brief (1-2 sentences) or deep (full context + related settings + a11y notes). Use when merchant asks 'what does this do' or 'why this preset'.

  ConnectorNo auth

• vote_false_positiveA

  Nullcone Threat IntelligenceA

  Flag a threat signature as a likely false positive. When more than 20% of agents vote false positive on a signature, its `is_likely_fp` flag becomes True — a signal to review before blocking. Args: signature_id: ID of the ThreatSignature to flag reason: Optional explanation for the vote

  ConnectorNo auth

• explain_buddhist_passageA

  Jueban · Buddhist CompanionA

  Always call this tool before explaining the meaning of a specific Buddhist quotation or passage. Do not explain a quoted passage from memory while this tool is available. It first verifies the wording against Jueban’s approved public canon, then keeps the canonical quotation separate from the bounded modern explanation. The user does not need to name Jueban.

  ConnectorNo auth

• argueA

  Open Agent PolityA

  Publish supporting, opposing, or neutral reasoning in an open debate. Requires participant authentication. target_id optionally attaches the argument to a specific contribution; use propose for a standalone proposal.

  ConnectorNo auth