OffshoreProz Agent Company

get_documents

Retrieve the DRAFT Agent Charter document suite for an Agent Company. Returns each instrument as Markdown plus a link to a single branded PDF pack. NEVIS suite: Articles of Organization, Operating Agreement, Agent Mandate & Authority Charter, Power of Attorney, Wallet Authority Schedule, Register of Members, Written Resolutions, Beneficial Ownership Declaration, Consent to Act, Risk/AML Policy, Indemnification Agreement, and a machine-readable mandate (JSON). WYOMING STANDALONE suite (the $299 tier): Formation Summary, Wyoming Operating Agreement (W.S. 17-29, with agent-delegation clauses), Agent Mandate & Authority Charter, Authority Resolution & Power of Attorney, Wallet Authority Schedule, Organizational Resolutions, US Tax & Compliance Memorandum (EIN, Form 5472/1065, WY annual report), and the machine-readable mandate. Available ONLY after payment is confirmed. Every document is a DRAFT for review by the OffshoreProz team and a licensed attorney.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_documents"
  }
}

Input Schema

Name	Required	Description	Default
`request_id`	Yes	The request_id (UUID) returned by create_formation_request or create_standalone_company.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the disclosure burden; it does state the draft-only nature, the attorney-review requirement, the Markdown plus single branded PDF pack return shape, and the payment gate. It omits behavior when payment is unconfirmed, permission/auth requirements, and error or partial-availability semantics for a mixed NEVIS/Wyoming suite.

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

Conciseness3/5

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

The front-loaded purpose is strong, but the bulk is a long inventory of document names that could be summarized or moved to the output. Roughly half the text is enumeration rather than decision-relevant guidance.

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?

No output schema exists, so the description usefully explains the return format (Markdown instruments plus one PDF link plus machine-readable JSON mandate) and the draft status. It is nearly complete for a one-parameter retrieval tool, missing only behavior for unpaid or unknown request_ids.

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 coverage is 100% and the single request_id parameter is fully documented as the UUID from create_formation_request or create_standalone_company. The description adds no meaning about how the suite selection (NEVIS vs Wyoming) relates to that request_id, so the baseline 3 applies.

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?

States a specific verb and resource ('Retrieve the DRAFT Agent Charter document suite for an Agent Company') and enumerates the exact instruments returned, so an agent knows precisely what it gets. It does not explicitly contrast itself with siblings such as get_formation_status, keeping it 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.

Usage Guidelines4/5

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

Gives a clear precondition that the Wyoming standalone suite is 'Available ONLY after payment is confirmed', which is real routing guidance. It offers no explicit alternatives or when-not-to-use guidance relative to the sibling status/requirements tools.

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.