OffshoreProz Agent Company

create_standalone_company

Form a STANDALONE US LLC (Wyoming or Delaware) — a real, state-filed company with its own EIN and registered agent. TWO packages: "agent_company" (default) bundles the Agent Charter (mandate, wallet authority, spending/risk limits) governing your AI agent; "standard_llc" is a REGULAR Wyoming LLC with an OPEN purpose (any lawful activity) and a standard document pack (Operating Agreement, resolutions, membership ledger, tax memo) — no Agent Charter, no agent spec required. Same price, same rails. TWO ways to pay: by CARD (returns a Stripe checkout_url the human owner opens) OR in USDC on-chain (the agent can pay autonomously). Returns a request_id and both payment options. Creates a REQUEST only — filing happens AFTER payment is confirmed. When an AI agent is involved it is an authorized delegate, never a member or a legal person; there is always at least one human principal.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_name": "<company_name>",
      "principal_office_address": "<principal_office_address>",
      "principals": "<principals>",
      "primary_contact": "<primary_contact>"
    },
    "name": "create_standalone_company"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	No	The autonomous AI agent the company owns and operates. REQUIRED for the agent_company package; omit for standard_llc. Never a member or a legal person.
`package`	No	"agent_company" (default): the full Agent Charter pack governing your AI agent — requires the agent field. "standard_llc": a regular Wyoming LLC with an OPEN purpose and a standard pack (Operating Agreement, organizational resolutions, membership ledger, US tax memo) — no Agent Charter; the agent field is ignored.	agent_company
`principals`	Yes	Human principal(s) who own the company. At least one. The agent is NOT listed here.
`callback_url`	No	OPTIONAL — an HTTPS endpoint the agent controls. We POST signed events there (payment.confirmed, filing.recorded, formed, annual_report.due) so you never need to poll get_formation_status. The create response returns the signing secret ONCE; verify X-OffshoreProz-Signature (sha256 HMAC of the raw body).
`company_name`	Yes	Desired company name (e.g. "Helios Capital"). "LLC" is appended for the filing.
`jurisdiction`	No	US state of formation. Wyoming only for now (Delaware coming soon). Wyoming: charging-order protection that extends to single-member LLCs (W.S. 17-29-503), no state income tax, and members stay off the public record.	wyoming
`tax_election`	No	"none" (default): default US tax classification (disregarded single-member / partnership). "c_corp": the LLC will elect on IRS Form 8832 to be taxed as a C corporation from formation — e.g. a non-US creator selling through a US platform (Microsoft, Apple, Roblox) who needs the company to give the platform a Form W-9 and stop 30% royalty withholding. The document pack then carries the corporate tax clauses, Form 8832 guidance, and — for a foreign sole owner — a services and IP assignment agreement.	none
`diagnostic_id`	No	If you ran agent_company_diagnostic first, pass the diagnostic_id it returned — links this formation to that assessment (helps us prioritize and pre-validate your intake).
`company_purpose`	No	Custom purpose clause for the Operating Agreement. Default: standard_llc → open purpose ("any lawful act or activity" under W.S. 17-29); agent_company → derived from the agent description.
`mailing_address`	No	Mailing address, if different from the principal office.
`primary_contact`	Yes	Human contact. Email is required (card buyer + document recipient).
`management_model`	No	Who manages the LLC. For agent_company, the agent is a delegate under the Agent Charter regardless of this.	member_managed
`ein_responsible_party`	No	Responsible party for the EIN (IRS SS-4). Do NOT include SSN/ITIN here — those are collected securely out-of-band.
`principal_office_address`	Yes	The LLC's principal office address (may be outside the US). Appears on the public Articles of Organization.
`company_name_alternatives`	No	Backup names in priority order, if the primary is unavailable at the state.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and does so: it states this creates a REQUEST only and that state filing happens after payment confirmation, that card payment returns a Stripe checkout_url for the human while USDC can be paid autonomously, that the response contains a request_id plus both payment options, and that the callback signing secret is returned once and events are verified via sha256 HMAC. It also pre-empts a legal/authority question by declaring the AI agent is an authorized delegate, never a member or legal person, with at least one human principal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core action and the two packages, and nearly every clause conveys a decision-relevant fact (packages, payment rails, request-only semantics, delegate status). Heavy ALL-CAPS emphasis and several compressed clauses make it denser to parse than necessary, but there is little true filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter, deeply nested creation tool with no annotations and no output schema, the description covers the missing behavioral layer well: what gets created, when filing occurs, what is returned, and how the async callback replaces polling. Remaining gaps are minor — no price or turnaround figures, and no explicit tie-break against the sibling create_formation_request.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the description largely restates the same package, jurisdiction, and tax_election semantics already documented in the schema. Its added value is limited to framing the cross-parameter dependency (agent required for agent_company, ignored for standard_llc) and the card-vs-USDC choice, so the baseline of 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: 'Form a STANDALONE US LLC (Wyoming or Delaware)', and immediately contrasts its two packages (agent_company vs standard_llc) and its two payment rails. What it doesn't do is name the closest sibling, create_formation_request, or explain how this standalone-company path differs from that generic formation request, so full sibling differentiation is missing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives real selection guidance: default to agent_company when an AI agent is involved, use standard_llc for an open-purpose regular LLC with no Agent Charter and no agent spec; pay by card when a human opens the Stripe URL, or in USDC for autonomous agent payment. It also routes the agent conditionally ('If you ran agent_company_diagnostic first, pass the diagnostic_id') and explains callback_url as an alternative to polling get_formation_status. It stops short of any explicit when-NOT-to-use or 'use X instead' statement.

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

All OffshoreProz Agent Company tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.