Skip to main content
Glama

Save Company Details

save_company_details
Destructive

Saves the company's post-payment details: industry and description, backup names, registered and mailing addresses, the IRS responsible party, and either an LLC's members with their ownership or a C-Corp's officers, directors and share structure. Every field is optional and is saved as given, so save each answer as soon as the user gives it; the response lists what is still missing. Refused with PRECONDITIONS_NOT_MET until verify_payment has confirmed payment, and with COMPANY_ALREADY_SUBMITTED once the formation is submitted, when changes go through doola support. Formation flow, in order: start_formation, create_checkout_session, verify_payment, save_company_details (industries from search_industries), submit_formation. Each response's nextStep is the step the flow now waits on.

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": "save_company_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
membersNoLLC only. Every member of the LLC, each a person. Replaces the saved members as a whole, so always send all of them. A company as a member is set up from the doola dashboard instead.
industryNoIndustry, verbatim from the search_industries list.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
descriptionNoWhat the business does, 50 characters max. Send with industry.
alternateNamesNoUp to two backup company names, without the LLC or Inc. suffix. The primary name is kept as saved.
mailingAddressNoWhere bank cards and IRS mail go. Must be in the US; use provider registeredAgent when the user has no US address.
shareStructureNoC-Corp only. The corporation's authorized shares and their par value.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.
sellingPlatformNoWhere the business sells, e.g. Amazon or Shopify. Optional.
executiveMembersNoC-Corp only. Every officer and director, each a person: at least one President, Secretary, Treasurer and Director, and at most one each of President, Secretary and Treasurer. Replaces the saved officers as a whole, so always send all of them.
responsiblePartyNoThe person the IRS treats as responsible for the company.
registeredAddressNoThe company's registered address in its formation state.

Output Schema

NameRequiredDescriptionDefault
codeNoStructured error code when error=true (e.g. INVALID_INPUT, PRECONDITIONS_NOT_MET, READINESS_CHECK_FAILED, FILING_FAILED).
errorNotrue if the call failed
savedNoWhat this call saved.
messageNoHuman-readable status.
missingNoPrerequisites still unmet, in flow order. Empty when only filing remains.
nextStepNoThe step the formation flow now waits on; null once formation is complete.
companyIdNoThe company the call acted on.
companyNameNoName of the company the call acted on. Name it to the user.
nextQuestionNoThe customer-facing question for nextStep; null once formation is complete.
conversation_idNoThis conversation's handle. Pass it unchanged as conversation_id on every later call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / message / description
      Previous value: -"Human-readable status or instruction."New value: +"Human-readable status."
    • removedOutput schema / properties / nextAction
      Removed value: -{
      -  "description": "Imperative for the agent — follow verbatim.",
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / nextActionInput
      Removed value: -{
      -  "description": "{tool, arguments} template for the next call. Replace every <placeholder> in arguments with the user's real answer.",
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • changedOutput schema / properties / nextQuestion / description
      Previous value: -"Question to ask the user verbatim before the next call."New value: +"The customer-facing question for nextStep; null once formation is complete."
    • changedOutput schema / properties / nextStep / description
      Previous value: -"The tool to call next; null when the flow is complete."New value: +"The step the formation flow now waits on; null once formation is complete."
    • addedOutput schema / properties / nextStep / properties
      Added value: +{
      +  "description": {
      +    "description": "Where the customer stands at this step and what their options are.",
      +    "type": "string"
      +  },
      +  "missingFields": {
      +    "description": "Arguments of that tool the step still needs.",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "tool": {
      +    "description": "The tool that records this step.",
      +    "type": "string"
      +  }
      +}
    • changedOutput schema / properties / nextStep / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "object",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / responsibleParty / properties / email / description
      Previous value: -"Email the SS-4 and Form 8821 are sent to for signing. Confirm it with the user; never a placeholder."New value: +"Email that receives any IRS forms that need signing (the SS-4, plus Form 8821 for Expedited EIN). Confirm it with the user; never a placeholder."
  3. Changed7 schema fields changed
    • changedInput schema / properties / alternateNames / description
      Previous value: -"Up to two backup company names, without the LLC suffix. The primary name is kept as saved."New value: +"Up to two backup company names, without the LLC or Inc. suffix. The primary name is kept as saved."
    • addedInput schema / properties / executiveMembers
      Added value: +{
      +  "description": "C-Corp only. Every officer and director, each a person: at least one President, Secretary, Treasurer and Director, and at most one each of President, Secretary and Treasurer. Replaces the saved officers as a whole, so always send all of them.",
      +  "items": {
      +    "properties": {
      +      "address": {
      +        "description": "Where the officer or director lives, with their phone.",
      +        "properties": {
      +          "city": {
      +            "description": "City",
      +            "type": "string"
      +          },
      +          "country": {
      +            "description": "ISO 3166-1 alpha-3 country code, e.g. USA, GBR, BRA.",
      +            "type": "string"
      +          },
      +          "line1": {
      +            "description": "Street address",
      +            "type": "string"
      +          },
      +          "line2": {
      +            "description": "Apartment, suite, etc. Optional.",
      +            "type": "string"
      +          },
      +          "phone": {
      +            "description": "Phone number with country code",
      +            "type": "string"
      +          },
      +          "postalCode": {
      +            "description": "Postal code",
      +            "type": "string"
      +          },
      +          "state": {
      +            "description": "State, province or region",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "line1",
      +          "city",
      +          "state",
      +          "postalCode",
      +          "country",
      +          "phone"
      +        ],
      +        "type": "object"
      +      },
      +      "legalFirstName": {
      +        "description": "Legal first name",
      +        "type": "string"
      +      },
      +      "legalLastName": {
      +        "description": "Legal last name",
      +        "type": "string"
      +      },
      +      "type": {
      +        "description": "The role this person holds. A person holding several roles is listed once per role.",
      +        "enum": [
      +          "President",
      +          "Secretary",
      +          "Treasurer",
      +          "Director"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "legalFirstName",
      +      "legalLastName",
      +      "address"
      +    ],
      +    "type": "object"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / mailingAddress / properties / provider / description
      Previous value: -"registeredAgent uses doola's Wyoming registered agent address (included); customer uses the address below."New value: +"registeredAgent uses doola's registered agent address in the formation state (included); customer uses the address below."
    • changedInput schema / properties / members / description
      Previous value: -"Every member of the LLC, each a person. Replaces the saved members as a whole, so always send all of them. A company as a member is set up from the doola dashboard instead."New value: +"LLC only. Every member of the LLC, each a person. Replaces the saved members as a whole, so always send all of them. A company as a member is set up from the doola dashboard instead."
    • changedInput schema / properties / registeredAddress / description
      Previous value: -"The company's Wyoming registered address."New value: +"The company's registered address in its formation state."
    • changedInput schema / properties / registeredAddress / properties / provider / description
      Previous value: -"registeredAgent uses doola's Wyoming registered agent address (included); customer uses the address below."New value: +"registeredAgent uses doola's registered agent address in the formation state (included); customer uses the address below."
    • addedInput schema / properties / shareStructure
      Added value: +{
      +  "description": "C-Corp only. The corporation's authorized shares and their par value.",
      +  "properties": {
      +    "authorizedShares": {
      +      "description": "Number of shares the corporation is authorized to issue, greater than 0.",
      +      "type": "integer"
      +    },
      +    "parValue": {
      +      "description": "Par value per share in USD, greater than 0, e.g. 0.00001.",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "authorizedShares",
      +    "parValue"
      +  ],
      +  "type": "object"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id
      Added value: +{
      +  "description": "This conversation's handle. Pass it unchanged as conversation_id on every later call.",
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations mark this as a mutating, destructive, closed-world write; the description adds the behavior an agent actually needs beyond that: every field is optional, values are stored verbatim with no validation round-trip, and the response reports what is still `missing` plus a nextStep. The gating error codes and the post-submission lockout are genuine behavioral context not present in 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?

Front-loaded with the saved fields, then the save-as-you-go instruction, then the preconditions, then the flow order — a sensible priority order with no filler. The single dense paragraph is long for a tool description, and the trailing nextStep sentence slightly repeats the flow sentence, but nothing is waste.

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 13-parameter nested mutation with an output schema, the description covers the pieces an agent cannot get from structure alone: optionality, verbatim persistence, precondition failures, sequential flow position, and what the response reveals. Return-value detail is correctly left to the output schema rather than restated.

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 baseline is 3, and the description earns an extra point by adding cross-field semantics: industry ties to search_industries, description caps at 50 characters and ships with industry, and the LLC-versus-C-Corp fork determines which of members/executiveMembers/shareStructure applies. It stops short of covering nested-field details like the 100% ownership sum or the required officer roles, which only the schema documents.

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 names a specific verb (saves) and enumerates exactly which resources are written: industry/description, backup names, addresses, IRS responsible party, LLC members with ownership or C-Corp officers/directors/share structure. That inventory makes it unmistakable versus read-only siblings like get_company_info or get_company_formation_details.

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?

It states when to call (as soon as the user gives any answer, since all fields are optional), where it sits in the ordered formation flow (start_formation → create_checkout_session → verify_payment → save_company_details → submit_formation), and where industries come from (search_industries). It also names the exclusions: PRECONDITIONS_NOT_MET before payment and COMPANY_ALREADY_SUBMITTED after submission, with the manual route via doola support.

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.