"Guidance or resources for writing a proposal" matching MCP tools:

• 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

• cti_get_guidelinesA

  website-searchA

  Get Lenny Zeltser's expert CTI writing guidelines. Topics include tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance), handoffs (cross-server routing), methodology (the three subsections), fields (per-field guidance), and CTI-specific topics: attribution (full Six Signals prose), confidence (ICD-203 ladder), pyramid_of_pain, six_signals (signals table only), and anti_patterns. The general writing topics (tone/words/structure/executive_summary) now defer to `get_security_writing_guidelines` for the canonical Five Elements rules; CTI-specific content lives in the other topics. Pair the 'fields' topic with field_id for single-field guidance. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• adcritter_get_platform_overviewA

  AdCritter for BuildersA

  Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.

  ConnectorNo auth

• migrate_to_propelauth_frontendA

  PropelAuth Integration MCP ServerA

  Returns instructions for migrating to PropelAuth in a frontend framework such as React, JavaScript, TypeScript, or when using Next.js for just the frontend (e.g. client-side rendered). Guidance includes migrating from several auth providers, such as Clerk or Auth0. Each guidance will include documentation from the auth provider and PropelAuth. It is important to follow the instructions carefully to ensure a successful integration. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc. CRITICAL: If the current implementation uses a traditional OAuth/OIDC flow (e.g., via express-openid-connect, passport-auth0, or similar backend-managed session libraries), you MUST select 'OAuth' as the framework, regardless of the frontend library (React/Vue/etc.). Only select 'React' or 'Javascript' if the current implementation uses a frontend-only SDK (like @auth0/auth0-react) or if using fullstack Next.js.

  ConnectorNo auth

• migrate_to_propelauth_fullstackA

  PropelAuth Integration MCP ServerA

  Returns instructions for migrating from an existing auth provider to PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application. If the user is using Next.js as just a frontend (e.g. client-side rendered with or without server routes), use the migrate_to_propelauth_frontend tool. Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc

  ConnectorNo auth

• prepare_formA

  EmbossA

  Prepare a form from documents: a proposal of every answer with its source, what is missing, and where documents disagree, before writing, plus attachments for a package. Same inputs as fill_form_from_context (form_id for a form already in the library, or pdf_url/pdf_base64 for a new one, plus context_text and/or context_urls), but nothing is written into the PDF: read the proposal, answer what is missing, then commit. policy is safe (write high and medium confidence) or strict (high only). Returns a job_id and a proposal_id; poll get_job about every 20 seconds. Billed as one context fill; the first 5 each month are free. Optional retention: ephemeral or account_default (default: the account's own setting); it applies only when this call creates the form (pdf_url, pdf_base64 or library), since an existing form keeps the setting it was created with. Ephemeral processing: source and output documents are deleted 60 to 70 minutes after the last activity on a form. Pass dry_run=true to rehearse this call without doing it: nothing is stored, charged or sent, and no AI is used. The answer says whether the real call would succeed or be refused, what it would cost, and what a rehearsal cannot check.

  ConnectorOAuth

• get_ir_documentsA

  MetricDuck — Financial AnalysisA

  Retrieve IR earnings-PRESENTATION-DECK text — forward guidance, operational KPIs, and segment outlook that are ONLY in the company's investor-relations slide deck and NOT in the SEC 8-K/10-Q release text or XBRL. Reach for this when get_metric_history / get_xbrl_facts have no series for a KPI or guidance figure, or the 8-K earnings release from get_filing_section lacks it (decks are a separate source): production or revenue guidance ranges, segment/division outlook, KPIs shown as slide charts (e.g., berth capacity %, Mboed production guidance, adjusted-EBITDA guidance). Use Cases: - "OXY Q3 2024 production guidance" -> get_ir_documents("OXY", fiscal_year=2024, fiscal_period="Q3", query="production guidance") - "NCLH berth capacity outlook" -> get_ir_documents("NCLH", fiscal_year=2021, fiscal_period="Q3", query="berth") - "KNTK adjusted EBITDA guidance range" -> get_ir_documents("KNTK", fiscal_year=2023, fiscal_period="Q3", query="EBITDA") Each deck returns its title, original IR url, a stable MetricDuck-hosted gcs_uri, and the matching slide text cited by page. Pass a `query` to land on the exact page; omit it for a bounded prefix of the latest deck. Resolve by ticker or cik; narrow with fiscal_year/fiscal_period.

  ConnectorAPI key

• compass_opportunities_acceptA

  ZeroWidthB

  The review verb for the Inbox: promotes an AI-PROPOSED opportunity (from compass_opportunities_propose or the opportunity scout) into the workspace's own pipeline. compass_opportunities_set_status does NOT do this — a proposal stays in the Inbox until accepted. Optional `status` decides its lane in the same step (BACKLOG to park it, EXPERIMENTING to start it); omitted, it lands in NEW. Fails with not_proposed when the row isn't an AI proposal. Ids come from compass_inbox_list / compass_opportunities_list. May return `needs_confirmation` — name the proposal and wait.

  Connector

  Destructive

  No auth

• review_proposalA

  Worthune Verified Financial ModelsA

  Decide one pending proposal. APPROVER OR OWNER KEY ONLY: developer and viewer keys are refused, so the key that configures mandates cannot sign off their output. approve executes nothing; it writes one signed projected-value ledger entry (a re-pin proposal moves the mandate to the newer profile version instead). reject needs a reason: not-material, client-preference, timing, data-is-wrong, already-done, or other (with a note). Refused when the proposal is not pending, has expired, or the household changed since it was computed. An agent should only call this when the person it acts for has made the decision. Same as POST /api/v1/proposals/{id}/approve and /reject.

  ConnectorNo auth

• get_hypothesisA

  Lacuna Research MCPA

  Fetch a generated novel ML/AI research proposal from Lacuna. Use after search_lacuna(search_type="hypothesis") to inspect a proposal. view selects the response shape: - "context" (default, recommended): compact single-fetch proposal context — summary_markdown, abstract, and linked directions, with the raw upstream record (whose markdown duplicates summary_markdown) dropped server-side. - "full": the server's version record, including version history and signal counts. Proposal bodies are in versions[].markdown. Use only when you need versions or signals.

  ConnectorNo auth

• folkmoot_voteA

  FolkmootA

  Cast or revise your sealed ballot on an open Folkmoot proposal: choice (one option id or label from the proposal, or no_change) or a ranking of several, most preferred first (counted with the Schulze method), with a 40-600 character rationale; the vote item in join's first_steps and in home carries the proposal_id. Use after reading the proposal and its pre-mortem: other agents' arguments open only after your first, blind ballot, and one revision citing one of them (because_argument_id) is allowed before close; tallies stay sealed until the proposal closes. Visitors' and new members' ballots are advisory; the same ballot sent twice is recorded once. Returns recorded, binding and closes_at. Example: {"proposal_id":"pr_7k2m","choice":"no_change","rationale":"Fewer pile-ons do not outweigh slower threads."} or {"proposal_id":"pr_7k2m","ranking":[2,0,1],"rationale":"..."}.

  ConnectorNo auth

• auto_schedule_proposalA

  OnplanaB

  PRO+ AI scheduling tool for agents. Proposes a new schedule for a project that fits all tasks before a target deadline while respecting dependencies. Designed for multi-turn agent workflows: call with mode="preview" to generate and present the proposal to the user, then call with mode="apply" once the user confirms. APPLY captures a "Before AI Schedule Proposal" baseline and commits all proposed dates in one atomic operation (requires project Owner or Manager role). Optionally levels resources to avoid overallocation. Cap: 100 tasks. Feature: aiAdvanced (PRO+).

  Connector

  Destructive

  OAuth

• upload_library_documentA

  OnplanaB

  Upload an existing file (PDF, Word/Excel/PowerPoint, an existing markdown/text/CSV file, or an image) into a project, proposal, or organization (tenant-level) document library from base64 content. Provide libraryId (create one first via create_library if needed), fileName incl. extension, mimeType, and contentBase64. Max 25 MB decoded. The bytes are magic-byte verified against the claimed mimeType (spoofed or disallowed types are rejected) and a WorkspaceDocument row is created exactly like a human upload. Use draft_document instead when you want to author markdown directly from a string. Requires project.content.create on the parent project (Viewers are read-only); for proposal libraries, a governance reviewer or the proposal submitter; for organization libraries, org.library.contribute (MEMBER+ by default).

  ConnectorOAuth

• PublishProposalRevisionA

  GraphOS MCP ServerA

  Save a new revision of a schema proposal by publishing changed subgraph schemas to its proposal variant, the same action as Save revision in GraphOS Studio. GraphOS composes the proposal variant, records the diff against the source variant, and runs schema checks on it. The source variant does not change. Send only the subgraphs that change, each with its full SDL. previousLaunchId must be the proposal variant's latest launch ID from GetProposal. If someone saved a revision since, the call fails, so read the proposal again before you retry. GraphOS saves the revision even when the schema does not compose, so this call succeeding does not mean the change is valid. Call GetProposal after the check finishes: latestRevision.checkWorkflow.status and latestRevision.launch.status show the result, and GetCheckResults takes the check ID for the details. Returns the proposal's new latest revision, or an error with a message. Provide the graph ID, the proposal variant name, previousLaunchId, a unique revision label, a summary of the change, and the subgraphs.

  Connector

  Destructive

  No auth

• generateAutomationProposalA

  Duvo MCPB

  Approve the current process map of a Module automation being set up and start writing the automation proposal from it, the same as the setup's Approve and continue in the web app. The proposal says what Duvo automates, what stays with the team and where work hands over. Returns 202 at once; the proposal takes a few minutes and appears on the setup's Automation Proposal step (`url`). Needs the team's own live current process map (call `generateAutomationProcessMap` first) and no proposal yet; `current_process_snapshot_id`, when given, must be that live map. Refused with 409 otherwise, or while required Policy questions are open or Duvo is already writing, and with 403 unless the caller created the process or is a Lead Builder or above. Confirm with the user before calling: say that approving the map writes the proposal from it. Next comes `approveAutomationProposal`.

  ConnectorNo auth

• check_permitted_developmentA

  AtlaslyA

  Purpose: prepare an England permitted-development evidence checklist, tentative class hint and restriction samples, without confirming a legal route. When to use: use for architect questions like "is this rear extension PD?", "can I convert this Class E shop to flats?", or "does Article 4 affect this loft conversion"; use check_planning_constraints when you only need raw constraints. Returns: pd_status always unclear, tentative candidate/applicable class, source states, sample flags, unknown counts and an authority-review checklist. All unresolved restriction evidence returns PD_EVIDENCE_UNAVAILABLE. Limitations: resolved England only; no legal applicability, current-law version, full-boundary intersection, dimensions, original building/use or permission-condition verification. Nearby records and null/small distances never prove containment or removal of a right. Source freshness/completeness are unverified; consult current legislation and the authority. The static keyword matcher is only a proposal hint. Parameter guidance: provide a full address/postcode and a concrete proposal phrase including use, works, and key dimensions where known. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the canonical site, coordinates, boundary confidence, LPA, evidence links, and project context.

  ConnectorNo auth

• get_security_writing_guidelinesA

  website-searchA

  Get Lenny Zeltser's expert writing guidelines for security reports and assessments. Provides guidance on tone, structure, clarity, executive summaries, and avoiding common writing mistakes. Includes rating-sheet items (the four lens sheets: structure, look, words, tone) as concrete reference points for grounded feedback. Works for any security document. This server never requests your documents and instructs your AI to keep them local—guidelines flow to your AI for local analysis. Note: For incident response reports specifically, use the ir_* tools which provide deeper section-by-section review criteria.

  ConnectorNo auth

• assessment_get_guidelinesA

  website-searchA

  Get Lenny Zeltser's expert security assessment report writing guidelines. Topics: severity (the risk-adjusted severity model — the spine), findings, remediation, methodology, scope, strengths, brief (one-page brief section guidance), executive_summary, analysis, anti_patterns, frameworks, handoffs, and summary. The general 'tone' topic defers to `get_security_writing_guidelines` for the canonical Five Elements rules. This server never requests your assessment notes or report and instructs your AI to keep them local—the templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• list_resourcesA

  flootA

  List the env vars a project's code can use and the resources behind them: (1) resources CONNECTED to the project — usable as process.env.<NAME> in endpoint code now; (2) the owner's other account-level credentials — reusable, but not usable in code until connected; (3) everything Floot can add. Call it to learn what env vars exist before writing backend code, and BEFORE provisioning or requesting any credential (the owner may already have the one you need). Pass query (case-insensitive substring over names, descriptions, types, and env var names) to filter when the account has many resources. Read-only. Details: get_guides('resources').

  ConnectorOAuth

• propose_asset_tradeA

  HundoA

  Propose a buy or sell trade for an asset. Returns a proposal id; to record it, call the confirm_proposal tool with the returned proposalId after the user approves (there is no UI button or proposal card to click in this context). To buy an asset the user does not hold yet, pass newAsset instead of assetId: confirming creates the asset and records the buy together. For sells, validates the user holds enough quantity. The cash account currency must match priceCurrency. Always include a short user-supplied description; optionally include a categoryId. MCP note: this tool only CREATES a pending proposal; nothing is recorded until confirm_proposal is called.

  ConnectorOAuth

• sheet_applyA

  SumOffice — real Word and Excel for agentsA

  Apply a proposal from sheet_propose_edits to the workbook in this session's cabin (not to your original file); the engine recalculates. Refused if the workbook revision moved on since the proposal — propose again. Repeating an applied proposal is a no-op.

  ConnectorNo auth