get_llc_optionsReturns the three US LLC formation packages offered by Start Companies, with price, turnaround time and everything each one includes, plus add-on services, annual renewals, tax advisory and how support works. Always call this before discussing prices, renewals, advisory or what is included.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds valuable context: the return contents (three packages, categories) and the prerequisite role. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. The first sentence front-loads the return contents, and the second provides a clear usage instruction. Every sentence is necessary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers all relevant aspects: what is returned (packages, pricing, inclusions, add-ons, renewals, advisory, support) and when to use it. No output schema exists, but the description compensates fully. The tool is simple (read-only, zero params), so completeness is high.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters; schema coverage is 100% trivially. The description does not need to explain parameters, and the baseline score of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the three US LLC formation packages with price, turnaround, inclusions, add-ons, renewals, tax advisory, and support. It specifies the source (Start Companies) and distinguishes from siblings like recommend_llc_package by positioning itself as the prerequisite call.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly instructs 'Always call this before discussing prices, renewals, advisory or what is included,' providing clear usage guidance. It does not list alternative tools or when-not-to-use, but the instruction is direct and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.