Skip to main content
Glama

Find the companies that share one company's building or c/o provider

find_colocated_companies
Read-onlyIdempotent

The companies sharing one company's address, given its UID: the same physical address, or the same c/o provider — the fiduciary it is domiciled at, matched as mailbox detection counts mass domiciliation. You pivot from a UID; a c/o string is never accepted. The subject is left out. Returns UIDs, newest first. basis names the keys it could be pivoted on, so an empty basis means no address and no provider, not that it stands alone.

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": {
      "uid": "<uid>"
    },
    "name": "find_colocated_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesCompany UID, formatted or plain
sizeNoPage size, max 100 (default 100)
cursorNonextCursor from the previous page; omit to start at the beginning. Opaque — pass it back verbatim, and keep the same filters and sort or it is rejected.

Output Schema

NameRequiredDescriptionDefault
dataYes
sourceYes
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changed
    • addedOutput schema / properties / data / properties / colocated / properties / page / properties / totalCapped
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / data / properties / colocated / properties / page / required
      Previous value: -[
      -  "size",
      -  "totalElements"
      -]New value: +[
      +  "size"
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, so the bar is lower, and the description still adds genuine behavior: the subject company is excluded from results, output is UIDs ordered newest first, and a `basis` field is returned naming the pivot keys. It stops short of describing limits like result caps or cost of mass-domiciliation address lookups.

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?

Purpose and pivot rule are front-loaded, and most clauses carry informational weight. The parenthetical about mailbox detection and mass domiciliation is somewhat dense and could be trimmed, but it explains why c/o providers are matched at all.

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?

An output schema exists, yet the description still explains the non-obvious return semantics — UIDs only, newest first, and the meaning of `basis`, including that an empty basis means no address and no provider rather than an isolated company. For a read-only, single-UID pivot tool, nothing an agent needs to call it correctly is missing.

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 all three parameters are already documented, giving a baseline of 3. The description adds meaning beyond the schema by constraining what `uid` may be (a company UID, never a c/o string) and by implying the result ordering that the opaque cursor depends on.

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?

The description states a specific verb and resource — companies sharing one company's address, keyed on that company's UID — and disambiguates the two match modes (same physical address vs. same c/o fiduciary provider). It also clarifies what it is not: a c/o-string lookup. That is enough for an agent to distinguish it from address-string or name-based siblings without opening schemas.

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 clear entry condition ("You pivot from a UID") and an explicit exclusion ("a c/o string is never accepted"), so the agent knows the required input modality. It does not, however, name a sibling alternative or state when another tool would be preferable, e.g. when the agent only has an address string.

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