Skip to main content
Glama

Corply — Start and run your company

by io.github.corply-dev
OverviewDiscussionsAdmin

Get formation status

get_status
Read-only

Return the formation status for a company (or its latest formation): founder-facing checklist, the payment block once documents exist, THIS caller's pendingSignatures + who else is awaitingOthers, postIncorp tasks, webDashboardUrl, nextStep, and an optional private celebration link after verified incorporation. Offer a newly discovered milestone once; trust nextStep over your own inference of what comes next. Before a new formation payment, billingCadence previews the exact required ongoing-plan disclosure without creating or changing checkout. Ask monthly versus annual once; annual includes 20% off Corply service fees. If the founder explicitly asks to remove phone, email, or domain before checkout, preview again with both billingCadence and removedOptionalServices; carry that same list into request_payment after fresh consent. Amendment balances preserve the existing historical terms and ignore previews; payment.disclosureBlocker reports any reconciliation needed before checkout. Prerequisite: authenticated active company access plus every prerequisite stated above. Canonicality: reads current server state and does not manufacture company facts. Idempotency: safe to repeat. Confirmation boundary: no additional confirmation is needed for this read, reversible save, explicit fact/evidence record, link preparation, plan refresh, or action pre-authorized by a standing founder-configured policy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdNo
formationIdNo
billingCadenceNoRead-only preview of the required ongoing plan as monthly or annual before payment. Paid or processing purchases retain their actual terms. Does not create checkout or change an active plan.
_corply_contextNo
removedOptionalServicesNoPass only after the founder explicitly asks to remove phone, email, or domain. Never offer, suggest, or infer removal. Omission keeps every optional service selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / annualRenewal
      Removed value: -{
-  "description": "Read-only preview of the requested renewal choice before payment. Paid or processing purchases retain their actual terms. Does not cancel or change an existing renewal.",
-  "enum": [
-    "automatic",
-    "approval_required",
-    "tax_date",
-    "none"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / billingCadence
      Added value: +{
+  "description": "Read-only preview of the required ongoing plan as monthly or annual before payment. Paid or processing purchases retain their actual terms. Does not create checkout or change an active plan.",
+  "enum": [
+    "monthly",
+    "annual"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / removedOptionalServices
      Added value: +{
+  "description": "Pass only after the founder explicitly asks to remove phone, email, or domain. Never offer, suggest, or infer removal. Omission keeps every optional service selected.",
+  "items": {
+    "enum": [
+      "phone",
+      "email",
+      "domain"
+    ],
+    "type": "string"
+  },
+  "maxItems": 3,
+  "type": "array"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / annualRenewal
      Added value: +{
+  "description": "Read-only preview of the requested renewal choice before payment. Paid or processing purchases retain their actual terms. Does not cancel or change an existing renewal.",
+  "enum": [
+    "automatic",
+    "approval_required",
+    "tax_date",
+    "none"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • removedInput schema / properties / _corply_context / description
      Removed value: -"Echo context_engineering.context_session from the prior Corply result."
  4. Changed1 schema field changed
    • addedInput schema / properties / _corply_context
      Added value: +{
+  "additionalProperties": false,
+  "dependentRequired": {
+    "receipt": [
+      "id"
+    ]
+  },
+  "description": "Echo context_engineering.context_session from the prior Corply result.",
+  "properties": {
+    "id": {
+      "maxLength": 200,
+      "minLength": 16,
+      "type": "string"
+    },
+    "receipt": {
+      "maxLength": 2048,
+      "minLength": 16,
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  5. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive), and the description goes well beyond them by stating the auth prerequisite, canonicality (reads current server state, does not manufacture facts), idempotency (safe to repeat), and an explicit confirmation boundary. This is unusually rich disclosure of behavior an agent cannot get from structured fields.

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

Conciseness2/5

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

The purpose is front-loaded, but the description then sprawls into a dense stream of billing, amendment, and policy rules that mix concerns and are hard to parse. Several sentences are tangential to invoking this read and would be better placed in their own tools' definitions.

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 complex, multi-parameter tool with no output schema, the description enumerates the returned fields and the key behavioral boundaries, which is substantial coverage. Gaps remain around the two ID parameters and the exact shape of the returned status object, but overall it is complete enough to call correctly.

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 40%, so the description should compensate. It does explain billingCadence and removedOptionalServices usage (preview semantics, consent requirement, omission behavior), but companyId and formationId receive no meaning beyond their names, and the relationship between the two is never clarified.

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?

Opens with a specific verb+resource ('Return the formation status for a company ... or its latest formation') and then enumerates the fields returned, so the agent knows exactly what this read yields. It is distinguished from generic reads by its formation-specific scope, though it does not explicitly name a sibling it differs from.

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?

Guidance is present but is almost entirely conditional rules about parameters (when to pass billingCadence, when to pass removedOptionalServices, carrying the list into request_payment) rather than when to choose this tool over alternatives like get_formation_revisions or get_company_briefing. Usage is implied through the workflow narrative rather than stated as tool selection.

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

All Corply — Start and run your 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