Skip to main content
Glama

Get Dissolution Price

get_dissolution_price
Read-only

Returns what closing (dissolving) the company with doola costs, as the dissolution review in the dashboard adds it up before any promotion: doola's fee, the state filing fee, the total and the optional Short Year Tax Return, with startDissolutionLink where the user starts it. When canStartDissolution is false, give no price and explain note; for a request already submitted call get_dissolution_status. Never give a figure the result does not contain. 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_price"
  }
}

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.4/5.0
Behavior4/5

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

With readOnlyHint and non-destructive already declared, the description still adds real behavioral context: the exact composition of the returned quote, the conditional branch keyed on canStartDissolution, the startDissolutionLink handoff, and the no-fabricated-figures guardrail. It does not cover error conditions or what happens if no dissolution review exists, which keeps it short of a 5.

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?

Content is front-loaded and every clause is functional — the field inventory, the conditional rule, the sibling handoff, and the output constraints. The first sentence is long and packs several ideas together, which slightly hurts scannability, but nothing is filler.

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?

There is no output schema, so the description compensates by enumerating the result's fields and the link field, and it specifies the negative branch and the correct alternative tool. Nothing an agent needs in order to call this and report the result correctly is missing.

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 (context, llm_model, conversation_id) are analytics-only and fully documented in the schema at 100% coverage, so the description adds nothing about them and needs to add nothing. 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 opening sentence names a specific resource (dissolution price) and enumerates exactly what it returns: doola fee, state filing fee, total, optional Short Year Tax Return, and startDissolutionLink. It also explicitly separates itself from get_dissolution_status, so an agent can pick between the two without opening either schema.

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 gives explicit exclusion rules: when canStartDissolution is false, withhold any price and explain the note instead; for an already-submitted request, route to get_dissolution_status. It also carries a hard usage constraint (never state a figure absent from the result) and a presentation rule (plain language, no field names).

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.