Skip to main content
Glama

Search doola Help Center

search_doola_help_center
Read-only

Searches doola's help center for how doola's services, prices, timelines and dashboard work, e.g. 'how long does an EIN take' or 'what does the registered agent service include'. Returns the most relevant passages with their article title. Use it for general questions about doola; for the user's own company, EIN, documents, invoices or deadlines, call the matching account tool instead. The passages are background, so prefer an account tool's answer when the two disagree. When the user asks for a person or human support, call get_support_options.

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": {
      "query": "<query>"
    },
    "name": "search_doola_help_center"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe question or topic to search for, in plain words, e.g. 'how long does an EIN take'
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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: results are passages plus article titles, and those passages are explicitly 'background' — subordinate to authoritative account data. It does not mention result counts, ranking, or what happens on an empty match, 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.

Conciseness5/5

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

Purpose and return shape are front-loaded, followed by routing rules in descending order of importance. Every sentence carries distinct information — none rephrases the name or the annotations — and the closing escalation pointer is one clause, not a paragraph.

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?

With no output schema, the description supplies the return shape (relevant passages with article titles) and their authority level. Combined with explicit sibling routing and the human-support escape hatch, an agent has everything needed to decide and call correctly.

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?

Schema description coverage is 100%, so query, context, llm_model and conversation_id are all documented in the schema, including the analytics-only nature and the no-PII warning. The description restates the query format with the same example already in the schema, adding no meaning beyond it, so the baseline of 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?

Names a specific verb and resource ('Searches doola's help center'), scopes it to services, prices, timelines and dashboard topics, and gives two concrete example queries that make the retrieval target unambiguous. The statement that it returns 'the most relevant passages with their article title' further pins down what kind of result to expect.

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?

Explicitly separates two cases: general doola questions go here, while the user's own company, EIN, documents, invoices or deadlines should route to the matching account tool. It also names get_support_options as the destination for human-support requests and adds a precedence rule when help-center passages conflict with account data.

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.