Skip to main content
Glama
Sign In

OffshoreProz Agent Company

by io.github.tcgtracker-boop
OverviewDiscussionsAdmin

reserve_company_name

FREE, no API key. For when the owner is NOT yet ready to form: softly hold a company name in our intake for 14 days. IMPORTANT — a hold does NOT secure the name; only filing does. If you are ready, skip this and call create_standalone_company directly: it returns a card checkout link AND an exact USDC/USDT amount the AGENT can pay autonomously in the same session, and filing starts the moment payment lands — no email, no human round-trip. This tool always returns that direct form-now path so you can proceed immediately; the hold is only a fallback for the not-ready case.

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>"
    },
    "name": "reserve_company_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_nameYesThe desired company name (e.g. "Helios Capital"). "LLC" is appended at filing if missing.
jurisdictionNoWhere the company would be formed. Wyoming only for now.wyoming
contact_emailNoRECOMMENDED — your human owner's email. We confirm the hold and notify before it lapses.
agent_descriptionNoOne line on what the agent does (helps us pre-clear the purpose).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 behavioral burden and does most of it: free, no API key, 14-day hold, explicitly non-binding ('a hold does NOT secure the name'), and notification before lapse via contact_email. It leaves a couple of gaps an agent would want — what happens to the name when the hold lapses, and whether duplicate or conflicting names are detected — but the important safety caveat is stated outright.

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 purpose and the 14-day scope are front-loaded, which is good, but the sales-style pitch for create_standalone_company is restated twice ('no email, no human round-trip' and 'always returns that direct form-now path'), spending roughly a third of the text on promotion rather than on this tool's behavior.

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 and no annotations, but the description covers cost, auth, hold duration, non-binding semantics, and notification behavior. The main missing piece is what the tool actually returns on success (confirmation, lapse date) and what a lapsed hold means for the agent's next step.

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%, so the schema already documents all four parameters including the LLC-appending rule and the Wyoming-only enum. The description adds no parameter-level detail beyond the schema and does not mention agent_description at all, so the baseline 3 applies.

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?

States a specific verb and resource with scope: 'softly hold a company name in our intake for 14 days.' It explicitly distinguishes itself from the sibling create_standalone_company, so an agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when: the owner is NOT yet ready to form. Gives an explicit when-not plus the alternative: if ready, skip this and call create_standalone_company, with a reason (checkout link, exact USDC/USDT amount, filing starts on payment). No inference required.

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