Skip to main content
Glama

Get doola Service Offers

get_service_offers
Read-only

Returns doola's services and its partners' offers for one serviceCategory, each with its sign-up link and the deal that matches the company's doola plan. doola services: ITIN, Bookkeeping, Amendments, DBA, Dissolution, Foreign Qualification, Certificate of Good Standing, Tax/Annual Report. Partner services: Banking, Business Insurance, Legal, Payroll and HR, Lending, Sales Tax, Trademark registration, Website, Payments, Mail, Phone (a US business phone number), E-Commerce, Cloud Services, Marketing. Pass one of these names. Use it when the user asks what doola can do for them or needs one of these services. Share each offer with its own link, exactly as returned, never invent a price or a deal, and follow the notes the answer carries. For doola's ITIN service, check get_itin_status first and mention it only when that allows the offer. Answer in plain language and never show the user the field names.

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": {
      "serviceCategory": "<serviceCategory>"
    },
    "name": "get_service_offers"
  }
}

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.
serviceCategoryYesservice category name to search for — use one of the available categories listed in the tool description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false/destructive=false, but the description adds substantial non-structured behavior: share links exactly as returned, never invent a price or deal, follow the answer's notes, answer in plain language, and never expose field names. These are output-handling constraints an agent could not infer from the safety hints alone.

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 purpose and categories, then pivots cleanly into usage and output rules; nothing is redundant. The category lists are long but justified because there is no enum, though the parenthetical '(a US business phone number)' and some repeated output-formatting clauses add mild bulk.

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 read-only lookup with no output schema, the description covers what is returned (offers, sign-up link, plan-matched deal) and how to present it, which is exactly the gap an absent output schema would otherwise leave. The analytics parameters are fully documented in the schema, so their omission from prose is not a deficiency.

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 would be 3, but the description supplies the allowed serviceCategory values ('Pass one of these names') which the schema does not encode as an enum. That is real added meaning, though it still says nothing about the three analytics parameters beyond what the schema already states.

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 ('Returns doola's services and its partners' offers for one serviceCategory') and then enumerates every valid category, so an agent knows exactly what domain this covers. It also carves out the ITIN case relative to sibling get_itin_status, distinguishing itself from at least one neighbor.

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?

Gives explicit selection conditions: 'Use it when the user asks what doola can do for them or needs one of these services', plus a concrete alternative path ('For doola's ITIN service, check get_itin_status first and mention it only when that allows the offer'). This is when-to-use and when-to-check-something-else guidance in one place.

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.