Skip to main content
Glama
Sign In

OffshoreProz Agent Company

by io.github.tcgtracker-boop
OverviewDiscussionsAdmin

get_compliance_calendar

Return the upcoming compliance obligations for an Agent Company, computed from its formation date. NEVIS companies: registered-agent + government renewal (with fee and USDC payment address), beneficial-owner update rules, and — if a Wyoming USD subsidiary was elected — the Wyoming annual report and US IRS Form 5472. WYOMING STANDALONE companies ($299 tier): the WY annual report (first day of the anniversary month, $60 minimum license tax), registered-agent renewal, and the federal filing that applies (Form 5472 + pro-forma 1120 for a foreign-owned single-member LLC; Form 1065 for multi-member). Use this to keep the entity in good standing year over year.

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_compliance_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesThe request_id (UUID) returned by create_formation_request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that results are derived from the formation date, branch by entity type, and include fees, a USDC payment address, and specific form numbers. It does not state read-only status explicitly, how pending/unformed entities are handled, or how far ahead 'upcoming' reaches.

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?

Purpose is front-loaded in the first sentence, followed by structured per-entity detail that is dense but each clause carries real informational weight (fees, forms, deadlines). Slightly long but justified by the branching return content.

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 one-parameter read tool with no output schema or annotations, the description thoroughly explains what the response will contain for each entity type. The remaining gap is the ambiguous time horizon of 'upcoming' and no mention of error behavior for an invalid or unformed request_id.

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 schema already documents that request_id is the UUID from create_formation_request. The description adds no parameter-level detail beyond that, so the schema does the work.

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

Purpose5/5

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

Specific verb and resource ('Return the upcoming compliance obligations for an Agent Company') plus scoping logic ('computed from its formation date'). It explicitly distinguishes the two entity types (NEVIS vs. WYOMING STANDALONE) and their divergent obligations, so an agent understands the tool's output varies by entity without opening the schema.

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

Usage Guidelines3/5

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

The closing sentence ('Use this to keep the entity in good standing year over year') implies the use case but gives no explicit when-to-use versus siblings such as get_formation_requirements or order_annual_report. It never says this is the read/planning tool while order_annual_report is the action tool.

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 toolsInspect
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.

Resources