Skip to main content
Glama

Get Company Addresses

get_company_addresses
Read-only

Returns the company's registered address (type business) and its mailing address, as the Company page of the doola dashboard shows them. provider registeredAgent means the address is doola's registered agent address in the formation state, which is what to answer when the user asks for their registered agent address; customer means the user gave their own. A message instead means no address is on file yet. 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_company_addresses"
  }
}

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

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real value: it decodes the provider field semantics (registeredAgent vs. customer) and explains the empty-state message. It does not cover auth or rate-limit behavior, but for a read-only lookup those are minor.

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?

The return shape is front-loaded in the first sentence, followed by field interpretation and then a short output-style instruction. It is slightly dense but every sentence carries information the agent needs to answer correctly.

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 carries the burden of explaining the return value — and it does: both address types, the provider value meanings, and the message fallback are covered. It also tells the agent how to present results in plain language without exposing field names, which is complete for a zero-required-param read tool.

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 are analytics-only metadata and are fully documented in the schema (100% coverage), so the baseline of 3 applies. The description adds no parameter-level detail because none of the parameters affect the tool's result, which is acceptable here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a concrete verb and resource: it returns the company's registered address (type business) and mailing address as shown on the dashboard's Company page. An agent can immediately tell this is an address-retrieval tool distinct in subject matter from siblings like get_company_formation_details or get_company_info, though it never explicitly names an alternative to avoid.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a direct routing rule: 'provider registeredAgent ... is what to answer when the user asks for their registered agent address,' which tells the agent exactly which user question this tool resolves. It also handles the empty case ('A message instead means no address is on file yet'), though it gives no explicit when-not-to-use or named alternative.

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.