Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

apollo_enrich_organization

Read-only

Enrich a company from its domain (firmographics, size, industry…).

Returns the exact estimated_num_employees, its per-department split (departmental_head_count), 6/12/24-month headcount growth, revenue, founding year and tech stack. Costs 1 Apollo credit. For several companies at once, prefer apollo_bulk_enrich_organizations (same cost, 10× fewer calls).

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": {
      "domain": "<domain>"
    },
    "name": "apollo_enrich_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
domainYes
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with that. It adds information annotations cannot convey: the call costs 1 Apollo credit and enumerates the substantive payload fields (estimated_num_employees, departmental_head_count, 6/12/24-month growth, revenue, founding year, tech stack). It does not mention failure modes for unknown domains or any rate limits.

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?

Three short sentences: action, payload, routing. The what-it-does statement is front-loaded and the credit cost and bulk alternative are placed where an agent will read them before acting. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 usefully enumerates what comes back, which is exactly the right compensation. It is slightly incomplete on the multi-tenant context parameters, which are only documented in the schema (and in French), but nothing essential about the enrichment itself is missing.

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 coverage is 83%, so the schema already documents the required 'domain' plus the contextual _org/_project/_run_id/_instance tokens. The description clarifies that the domain is a company domain being enriched, but adds no syntax details (bare domain vs URL, subdomains) and says nothing about the context parameters that gate the call.

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 ('Enrich a company from its domain') plus the data categories returned (firmographics, size, industry), which distinguishes it immediately from apollo_search_organizations and apollo_match_person. The final sentence even names the sibling it should not be confused with.

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?

Gives an explicit routing rule: for several companies at once use apollo_bulk_enrich_organizations because it is the same cost with 10x fewer calls. There is no guidance on prerequisites (an org/project token, an active run for _run_id) or on when a search or match tool would be a better entry point.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tulina toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources