"Bitbucket pull request reviewer information" matching MCP tools:

• get_document_cost_tool

  Bankruptcy Observer

  Preview the cost to download a court filing PDF. Identify the entry with docket_id (preferred) or simple_name + item_number (legacy connectors). Does not pull the document and does not charge. Same preview as get_document_tool when accept_charge/download is omitted. Confirm the cost with the user before download. Free pages come from the plan limitDocuments allowance (not MCP monthly request limits). Returns page_count, chargeable_pages, cost (0 if already purchased), plan_limit_documents, pages_used_this_period, free_pages_remaining, and already_owned.

  Connector

• upsert_note

  OpenAkashic

  Create or overwrite an OpenAkashic markdown note. kind='claim' notes enter the contribution flow as private drafts with publication_status=requested. Sagwan then runs the first-pass guardrail: requested -> guardrail_passed or guardrail_rejected. A passed claim can later be approved/published by the publication workflow; rejected claims stay private with reviewer notes in frontmatter. Prefer claim for atomic reusable findings; Sagwan can later turn multiple related claims into a capsule. kind='capsule' notes stay private until you request publication review. Other kinds (playbook, concept, etc.) remain Closed-only working memory. Writable roots: personal_vault/, doc/, assets/ only. Formerly known as `check_contribution_status`: use claim_contribution_status to check submitted claim state. If you see tool-not-found errors for the old name, use claim_contribution_status instead. IMPORTANT: The response includes `path` — save this value and pass it to request_note_publication when you want to submit a capsule/synthesis for public review.

  Connector

• chieflab_create_next_move_action

  ChiefLab

  P75 — turn a Next Move suggestion into an approval-gated draft action. USE WHEN you've called chieflab_suggest_next_move and the suggestion's kind is not 'wait' or 'noop'. Creates an actionStore entry with status='awaiting_approval', the suggested draft body inline, and an executionMatrix that points at the right next-execution path. The reviewer sees the new card in the Launch Room / IDE chat like any other approval card — same approve / revise / reject flow. Closes the loop: launch → measure → next move → approve → execute → repeat.

  Connector

• resolve_comment

  Dock

  Mark a comment thread resolved. Idempotent: calling on an already-resolved thread returns the existing `resolvedAt` unchanged. Fires `comment.resolved`. Pair with `unresolve_comment` for the reverse. Used by agents to close a feedback thread once they've iterated on the change the reviewer asked for.

  Connector

• get_uploaded_image

  GlanceAI Fashion MCP

  Retrieve the image the user most recently uploaded via the `upload_image` tool as an image block for analysis. WHEN TO CALL: Immediately after the user confirms their upload (message says 'Image uploaded successfully'). WHAT TO DO AFTER: Analyse the image and continue the original flow — describe what you see, extract style/colour/product details, and use that information to fulfil the user's request. Never wait for further instruction before analysing.

  Connector

• get_block_info

  blockscout-mcp-server

  Get block information like timestamp, gas used, burnt fees, transaction count etc. Can optionally include the list of transaction hashes contained in the block. Transaction hashes are omitted by default; request them only when you truly need them, because on high-traffic chains the list may exhaust the context.

  Connector

• chieflab_review_visual_asset

  ChiefLab

  P104 — approve or reject a single visual asset (LinkedIn graphic / X image / landing hero / Product Hunt gallery / carousel slide). USE WHEN a reviewer hits 'Approve' or 'Reject' on a launch image in the Launch Room. Reads the run's stored visualAssets list, updates the matching asset's status (approved | rejected | pending_approval), persists the change to run metadata so future loads + the channel-media render reflect the decision. Companion to chieflab_regenerate_visual_asset (which produces an updated asset shape without persisting).

  Connector

• gribstream_validate_request

  GribStream MCP

  NO AUTH / PUBLIC / READ-ONLY. Validates the basic shape, exact selector tuples, and expression syntax of a proposed GribStream /timeseries or /runs request without sending it. This tool does not execute the request, query weather values, or return forecast data. Use this before returning any hand-edited curl or when changing a request from one dataset to another.

  Connector

• search

  Library

  Search MCP servers by server title/name, description, or by the tools they provide. Accepts natural language capability queries like 'send emails', 'search the web', 'create pull requests', or direct server names like 'GitHub' or 'Stripe'. Results are ranked by relevance: title match first, then tool name match, then description. Each result includes the server's tool list so you can confirm it does what you need. Set limit based on the type of request you received: - Prompting (general/exploratory — user is browsing or asking broadly): use 20-30 - Task assignment (user delegated a goal for you to execute autonomously): use 10-15 - Instruction/directive (specific command with a clear target server in mind): use 3-5

  Connector

• chieflab_create_next_move_action

  ChiefLab

  P75 — turn a Next Move suggestion into an approval-gated draft action. USE WHEN you've called chieflab_suggest_next_move and the suggestion's kind is not 'wait' or 'noop'. Creates an actionStore entry with status='awaiting_approval', the suggested draft body inline, and an executionMatrix that points at the right next-execution path. The reviewer sees the new card in the Launch Room / IDE chat like any other approval card — same approve / revise / reject flow. Closes the loop: launch → measure → next move → approve → execute → repeat.

  Connector

• chieflab_regenerate_visual_asset

  ChiefLab

  P72 — regenerate a single visual asset (LinkedIn graphic, X graphic, landing hero, etc.) with a different style / fidelity / headline / model. USE WHEN a reviewer hits 'Regenerate' on a launch image in the Launch Room. Reads the original launch's brief from the run metadata, calls produceVisualAsset with the new parameters, and returns the updated asset shape (assetId, dataUrl, dimensions, prompt, mode). Does NOT auto-persist back to the run — caller decides whether to swap the asset in place (via runStore) or treat the regen as a parallel candidate.

  Connector

• get_pet_request_info

  Codex Pets Registry

  Use when the user wants to request a new Codex pet or understand the public request form fields and reference image limits. Do not use to create, submit, update, or inspect private generation requests; no MCP tool exposes those operations. Use search_pets or get_pet for existing approved pets.

  Connector

• fvs_example_render_request

  Future Video Studio

  Return a minimal scene render request agents can adapt.

  Connector

• get_transaction_info

  mcp-server

  Get comprehensive transaction information. Unlike standard eth_getTransactionByHash, this tool returns enriched data including decoded input parameters, detailed token transfers with token metadata, transaction fee breakdown (priority fees, burnt fees) and categorized transaction types. By default, the raw transaction input is omitted if a decoded version is available to save context; request it with `include_raw_input=True` only when you truly need the raw hex data. Essential for transaction analysis, debugging smart contract interactions, tracking DeFi operations.

  Connector

• claim_contribution_status

  OpenAkashic

  Return the current contribution state for kind='claim' notes. Formerly known as `check_contribution_status`. If you see tool-not-found errors, use this name instead. Use this after submitting a claim with upsert_note(kind='claim') to check whether it is still requested, guardrail_passed, guardrail_rejected, or published. The response includes submission timestamp and reviewer notes when Sagwan or a publisher has written them.

  Connector

• get_block_info

  mcp-server

  Get block information like timestamp, gas used, burnt fees, transaction count etc. Can optionally include the list of transaction hashes contained in the block. Transaction hashes are omitted by default; request them only when you truly need them, because on high-traffic chains the list may exhaust the context.

  Connector

• get_transaction_info

  blockscout-mcp-server

  Get comprehensive transaction information. Unlike standard eth_getTransactionByHash, this tool returns enriched data including decoded input parameters, detailed token transfers with token metadata, transaction fee breakdown (priority fees, burnt fees) and categorized transaction types. By default, the raw transaction input is omitted if a decoded version is available to save context; request it with `include_raw_input=True` only when you truly need the raw hex data. Essential for transaction analysis, debugging smart contract interactions, tracking DeFi operations.

  Connector

• gribstream_resolve_shared_parameter

  GribStream MCP

  NO AUTH / PUBLIC / READ-ONLY. Resolves one shared parameter preset for a dataset, returning native variables and expressions to use in /timeseries or /runs request bodies. This tool does not execute the request, query weather values, or return forecast data.

  Connector

• ateam_sync_all

  ateam-mcp

  Sync ALL tenants: push Builder FS → GitHub, then pull GitHub → Core MongoDB. Requires master key authentication. Returns a summary table with results for each tenant/solution.

  Connector

• waveguard_scan_timeseries

  WaveGuard

  Detect anomalies in time-series data — use after pulling numeric metrics from monitoring APIs, financial data sources, IoT sensors, or spreadsheet columns. Send a single numeric array and specify a window size. Early windows define 'normal', recent windows are tested for anomalies. Typical workflow: (1) Pull a column of numbers from Sheets, a Supabase time-series table, or a metrics API. (2) Pass the array here. (3) Get back which time windows are anomalous. Examples: - Revenue monitoring: Pull monthly revenue from Sheets → detect anomalous months - Stock screening: Pull 90 days of closing prices → find unusual price windows - Server health: Pull response-time metrics → identify degradation windows - Sensor QA: Pull temperature readings from IoT API → flag sensor drift

  Connector