Skip to main content
Glama

Maple Minute

Start a company (unpaid order)

start_company

Start a company based in Ontario or British Columbia: federal (CBCA), or a BC or Ontario company. Works without an API key: then it returns the company with checkout_url, the person pays there or on page_url, and follows the company later by signing in at mapleminute.com with the contact email. With an API key the company joins that account (get_payment_link, get_company and the rest). Nothing is filed until payment. Ask the human for every detail; never invent names, addresses or consents.

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": {
      "contact": "<contact>",
      "office": "<office>",
      "people": "<people>",
      "business_activity": "<business_activity>",
      "directors_agreed_to_act": "<directors_agreed_to_act>",
      "agree_to_terms_and_privacy": "<agree_to_terms_and_privacy>"
    },
    "name": "start_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
dunsNoFree: we request a D-U-N-S number from Dun & Bradstreet once incorporated (needed for Apple/Google developer accounts and some suppliers); usually within 30 business days.
nameNoOmit for a numbered company (fastest; like 1234567 Canada Inc., 1234567 B.C. Ltd. or 1234567 Ontario Inc.).
officeYesRegistered office: public, a street address in the province, not a PO box.
peopleYesEveryone who is a director or owns part of the company.
contactYesThe person we talk to about the order. Receives the receipt, documents and private order link.
expressNoFederal only: Corporations Canada processes within 4 hours for a $100 government fee.
yearly_planNoWe file the annual returns and changes every year (price in get_prices).
jurisdictionNoCA: federal, name protected across Canada, also registered in the office's province; needs resident Canadian directors (at least 1, or a quarter with 4+). BC or ON: a provincial company; directors can live anywhere, the office must be in that province, no express. Moving a provincial company to federal later costs about $900 (BC) or $530 (ON) in government fees. Fees in get_prices.CA
president_indexNoIndex in people of the president; must be a director or an officer.
business_activityYesA few words, like "coffee shop" or "software consulting".
also_register_in_bcNoOnly when the office is in Ontario (federal or ON company): also register in BC (BC government fee, plus the BC name approval for an Ontario company, and our fee in get_prices; the yearly plan then adds the BC annual report). No office in BC is needed, but BC requires an attorney: an individual living in BC (at the BC office where they can usually be reached) or a BC company (at its registered office), who accepts legal papers for the company there. Only if the company does business in BC.
company_phone_numberNoA Canadian phone number for the company, from us (yearly fee, see get_prices). Receive-only: texts and voicemails show in get_company.phone. Keeps the founder's own number out of business directories.
directors_agreed_to_actYesEvery director is 18+, not bankrupt, and agreed to be a director. Only send true if the human confirmed it.
also_register_in_ontarioNoOnly when the office is in BC (federal or BC company): also register in Ontario. No government fee; our fee in get_prices. Only if the company does business in Ontario.
financial_year_end_monthNoThe company year ends on the last day of this month.
agree_to_terms_and_privacyYesThe human agrees to https://mapleminute.com/terms and https://mapleminute.com/privacy. Only send true if they confirmed it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses the crucial trait that nothing is filed until payment and that an unpaid order plus checkout_url is the initial result. It also states the authentication-dependent behavior difference and the follow-up access route through mapleminute.com, none of which appears in the annotations.

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?

The purpose is front-loaded and each sentence carries content: scope, anonymous flow, API-key flow, payment gating, and the no-fabrication rule. The middle sentences are dense and slightly compressed, but there is little wasted wording.

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

Completeness5/5

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

For a 16-parameter incorporation tool with no output schema, the description explains what is returned (company plus checkout_url) and what happens after payment, which is exactly what is missing from structured data. Combined with the fully documented schema, an agent has what it needs to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already carries parameter meaning and the baseline is 3. The description adds a real constraint on parameter values — ask the human for every detail and never invent names, addresses, or consents — which is directly relevant to the required identity and consent fields.

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?

The first sentence gives a specific verb plus resource and enumerates the exact scope (federal CBCA, BC, or Ontario company) that the tool covers. It is immediately distinguishable from get_company, get_payment_link, and list_companies, which are named only as downstream follow-ups.

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 clearly frames the two operating modes — no API key (returns checkout_url, payment on page_url, later sign-in with contact email) versus with an API key (company joins the calling account) — which tells the agent when this path is appropriate. It stops short of naming which sibling to use instead for post-incorporation actions, though those are implied as later steps.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources