Skip to main content
Glama

Get Dissolution Status

get_dissolution_status
Read-only

Returns the status of the user's request to dissolve (close) their company with doola, as the dashboard shows it: In Progress, Awaiting Payment or Completed, and the date it was submitted, plus the same for the Short Year Tax Return when they added it. When dissolutionOnFile is false there is no dissolution request: never suggest one is in progress. For why it is taking longer or what the state still needs, point the user to doola support. Answer in plain language and never show the user the field names.

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

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.
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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds substantial context beyond them: the finite set of status values, the meaning of the dissolutionOnFile flag, the Short Year Tax Return attachment case, and the explicit boundary that it cannot explain delays. It also constrains presentation ('Answer in plain language and never show the user the field names'), which annotations cannot 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?

The returned states and the false-flag rule are front-loaded, and each sentence carries functional content. The closing presentation instructions are useful but slightly bulk up a short status tool.

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?

With no output schema, the description does the work of explaining return values: status values, submitted date, the Short Year Tax Return case, and the empty-state flag. It leaves edge cases unspecified, such as what is returned when the user has no active company or when data has not yet been submitted.

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?

All three parameters are optional analytics-only fields with 100% schema description coverage, including the 'never include personal details' and conversation_id reuse rules. The description adds nothing about them, but the schema already carries the full burden, so the baseline 3 applies.

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 description pairs a specific verb and resource ('Returns the status of the user's request to dissolve (close) their company') with the exact values returned (In Progress, Awaiting Payment, Completed) plus the submitted date. It also bounds the scope to the Short Year Tax Return 'when they added it', so an agent can distinguish this from the tax-filing and formation siblings without opening a schema.

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 gives explicit negative guidance ('When dissolutionOnFile is false there is no dissolution request: never suggest one is in progress') and a routing rule for out-of-scope questions ('For why it is taking longer... point the user to doola support'). It stops short of naming an alternative tool for the adjacent tax-return status question, which is the only gap.

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.