Skip to main content
Glama

Aldro: small-business tax

Send the user's signup to Aldro

start_onboarding

Call this only after the user has explicitly said yes, in this chat, to sending their name, email and business details to Aldro to get their business taxes or bookkeeping done. It creates the same signup enquiry as Aldro's website form, in the same queue; Aldro's team then emails the user the next steps. Set consent to true only when the user agreed. Testing the tool? Set test to true. It is not a marketing opt-in and takes no payment. Limits: 5 signups an hour per connection, 25 a day in total.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "email": "<email>",
      "business_name": "<business_name>",
      "country": "<country>",
      "entity": "<entity>",
      "service": "<service>",
      "consent": "<consent>"
    },
    "name": "start_onboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe user's full name.
testNoOptional. true when you are testing this tool rather than sending a real user's signup. The enquiry is stored, marked as a test, and nobody emails it.
emailYesThe email address Aldro should reply to.
entityYesBusiness type. US: sole_prop, single_member_llc, multi_member_llc, partnership, s_corp, c_corp. Canada: sole_prop or corporation.
consentYestrue only if the user explicitly agreed in this chat to share these details with Aldro.
countryYesUS for the United States, CA for Canada.
messageNoOptional. Anything the user wants Aldro to know.
serviceYestax (yearly business tax filing), bookkeeping (monthly), both, or catch-up (behind on the books).
business_nameYesThe business's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / test
      Added value: +{
      +  "description": "Optional. true when you are testing this tool rather than sending a real user's signup. The enquiry is stored, marked as a test, and nobody emails it.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description goes well beyond that: it discloses the real-world side effect (an enquiry in Aldro's live queue), the human follow-up email, and concrete rate limits (5/hour per connection, 25/day total) that an agent must respect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences, front-loaded with the hard precondition, then effect, then flags, then limits. Nothing is filler; every sentence constrains agent behavior.

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?

A 9-parameter mutation tool with no output schema needs consent gating, side effects, and rate limits explained, and all three are present. An agent has everything needed to decide to call it and to call it correctly.

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. The description still adds cross-parameter intent — the consent flag must be true only on explicit agreement, and test=true suppresses the human email — though most of that is echoed in the schema's own property descriptions.

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?

States a specific verb and resource — it creates a signup enquiry identical to Aldro's website form, landing in the same queue. It also clarifies the downstream effect (Aldro's team emails the user next steps) and distinguishes itself from the read-only sibling info tools by being the only send action.

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?

Explicit gating: 'Call this only after the user has explicitly said yes, in this chat.' It also carves out what this is not (not a marketing opt-in, takes no payment) and gives a testing path via the test flag, so the agent knows both when to call and when not to.

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