Skip to main content
Glama

Submit Business Registration Data

submit_business_data
Destructive

Submit brand registration data for the onboarding process. All fields are optional — you can submit partial data and continue filling in the rest in subsequent calls.

USAGE PATTERN:

  1. Read user://current/onboarding_status to see the current status and any missing fields

  2. Collect fields conversationally (one or a few at a time — don't overwhelm the user)

  3. Call this tool with whatever fields you have collected so far

  4. Check the response: if 'missingFields' is present, continue collecting those fields and call again

  5. When all fields are provided, status transitions to 'SUBMITTED' automatically

  6. Re-read user://current/onboarding_status after each call to track updated missing fields

PARTIAL SUBMISSIONS:

  • This tool is fully idempotent and accumulates data across calls

  • Re-submitting a field updates it; other fields already collected are preserved

  • Status stays 'BUSINESS_DATA_PENDING' until all required fields are provided

COMPLETE SUBMISSION:

  • When all required fields are present, status becomes 'SUBMITTED'

  • Inform the user that carrier approval takes ~1 business day

  • Do NOT re-submit once status is 'SUBMITTED' or 'ACTIVE'

BLOCKED STATES:

  • Returns an error if status is already 'SUBMITTED' or 'ACTIVE'

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "submit_business_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationsNoMessage destination countries (at least one required)
companyCountryNoCountry code where company is based, e.g. US, CA
tollFreeVerificationFormNoBusiness verification and compliance information

Output Schema

NameRequiredDescriptionDefault
errorNo
successYes
newStatusNo
nextStepsNo
missingFieldsNo
estimatedApprovalTimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, it discloses that the call is idempotent, accumulates data, that re-submission overwrites only the supplied field while preserving others, and that status transitions occur automatically when required fields are satisfied. It also describes the blocked-state error and the downstream ~1 business day approval expectation, which the annotations do not convey.

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?

Section headers (USAGE PATTERN, PARTIAL SUBMISSIONS, COMPLETE SUBMISSION, BLOCKED STATES) front-load the workflow and make the text scannable. There is mild redundancy — step 6 about re-reading status overlaps with step 4's response check, and the partial-submission bullet repeats the 'all fields optional' statement — but nothing is bloated relative to the tool's complexity.

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?

An output schema exists, so return values need not be explained, yet the description still tells the agent to inspect 'missingFields' in the response, closing the loop between call and return. For a nested, stateful onboarding mutation, the definition covers preconditions, incremental calling, terminal states, and failure behavior.

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 every field (destinations, companyCountry, tollFreeVerificationForm and its nested properties) is already documented in the schema; the baseline of 3 applies. The description adds workflow context about partial submission and mentions 'required fields' without identifying which fields those are, leaving the caller to rely on the onboarding status or the schema's nested 'at least one required' note on destinations.

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?

The first sentence states a specific verb and resource: 'Submit brand registration data for the onboarding process,' which is unambiguous. It is clear about scope (registration data for onboarding) but never names or distinguishes itself from related onboarding siblings such as get_onboarding_status, though the surrounding usage pattern makes the relationship implicit.

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?

The description provides an explicit six-step usage pattern, including reading user://current/onboarding_status first, collecting fields conversationally, calling incrementally, and re-reading status afterward. It also states explicit when-not-to-use conditions ('Do NOT re-submit once status is SUBMITTED or ACTIVE') and describes the blocked-state error, leaving little to inference.

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