Skip to main content
Glama

Register a company

company_create

Registers a new company in your client portal and makes you its owner. An account can create up to 3 companies. The company starts unverified; documents are uploaded on the website. Call without confirm first for a preview, then again with confirm and the preview_token.

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": {
      "name": "<name>",
      "country": "<country>"
    },
    "name": "company_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
nameYesTrade name.
confirmNoSet true only on the second call, after the user approved the preview.
countryYesCountry as 2 uppercase letters, e.g. IQ.
legalNameNoRegistered legal name, if different.
preview_tokenNoThe preview_token returned by the first call (same input).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write. The description adds real context beyond that: the account quota of 3 companies, the unverified starting state, and the out-of-band document upload step. It stops short of describing failure modes or what the preview response contains beyond the token.

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

Conciseness5/5

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

Three sentences, front-loaded with the action and side effect, then constraints, then the call sequence. No filler and nothing repeated from the schema.

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 6-parameter mutation with no output schema, the description covers the quota, the verification state, the out-of-band document step, and the two-phase invocation. Only the shape of the preview response is left implicit, which is a minor gap.

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 83%, so the schema already documents most parameters. The description still adds value by explaining the relationship between confirm and preview_token as a two-call approval flow, which is the non-obvious semantic an agent needs to sequence the calls correctly.

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 ('Registers a new company in your client portal') plus a side effect ('makes you its owner'), which clearly separates it from company_update, company_get, and company_invite_create.

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 explicit procedural guidance: call without confirm for a preview, then again with confirm and the preview_token, and notes the 3-company cap and that documents are uploaded on the website rather than here. It does not name sibling alternatives or state when not to use it, so it falls short of a 5.

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