Skip to main content
Glama

WhiteIntel — Ownership Intelligence

by dev.whiteintel

graph_neighbourhood

Read-onlyIdempotent

Every ownership/control edge within a bounded number of hops of one entity, in BOTH directions — who it controls, who controls it, and their neighbours. Hard-capped in the database: depth 3, 300 edges, and at most 25 edges followed per entity per direction per hop. When the edge budget runs out the response sets truncated: true and says so — the corpus contains single entities with more than 22,000 edges, so a truncated view is normal for hubs, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootYesEntity uuid from search_entities / resolve.
depthNoHops, 1–3 (default 2). Also capped by the caller's plan.
edgesNoEdge budget, 10–300 (default 120).

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, but the description goes further by disclosing the hard caps (depth 3, 300 edges, 25 per entity per direction) and the truncation behavior with `truncated: true`, plus the possibility of normal truncation for hubs. This is valuable beyond annotations.

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?

The description is two sentences, tightly packed with essential information: what it returns, the caps, and the truncation behavior. No filler or redundancy; every sentence adds value.

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?

The tool is moderately complex with 3 parameters, but the schema covers them well, annotations cover the safety profile, and the output schema is absent. The description explains the output shape (edges, truncation flag) and the expected scale, making it complete for effective use. No gaps identified.

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% (all three parameters have detailed descriptions). The tool description adds context about the edge budget and truncation but does not add semantics beyond what the schema already provides (e.g., formats or constraints). Baseline 3 is appropriate.

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 clearly states the tool's purpose: retrieving ownership/control edges within a bounded number of hops, in both directions, from a given entity. It explicitly contrasts with siblings like graph_path and trace_ownership_path by highlighting the bidirectional neighbourhood walk and the hard-capped nature.

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?

The description implies usage for exploring the ownership neighbourhood around an entity, mentioning the direction (both) and the bounded scope. It does not explicitly name alternatives or state when not to use it, but the context signals make it clear for a graph traversal tool, especially given the sibling names.

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

All WhiteIntel — Ownership Intelligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have distinct purposes (search, lookup, get details, graph traversal, coverage maps, payment). Some overlap exists between lookup_company and lookup_by_identifier (both resolve identifiers, though one is UK-specific), and between get_entity vs get_company_details, but descriptions clarify distinctions. find_similar and semantic_search both find similar entities but different mechanisms.

Naming Consistency3/5

Uses a mix of verb_noun and noun_phrases: buy_dossier, claim_dossier, check_offshore_exposure, find_similar, get_pricing, get_pulse, graph_neighbourhood, list_asset_coverage, lookup_by_identifier, search_entities, trace_ownership_path. While most use underscores and verbs like get/lookup/search/list, there are inconsistencies like 'graph_neighbourhood' (noun start) vs 'trace_ownership_path' (verb start). Overall readable but not perfectly consistent.

Tool Count4/5

23 tools is at the high end but justifiable for a comprehensive intelligence server covering search, lookup, graph, coverage, payments, and entity details. 'buy_dossier' is considered one of the tools and adds bulk but not excessive. It is appropriate for the scope.

Completeness4/5

Covers a wide range: search (search_entities, search_companies, semantic_search), identifier lookup (lookup_by_identifier, lookup_company), entity details (get_entity, get_company_details, get_financials), graph (graph_neighbourhood, graph_path, trace_ownership_path), coverage maps (list_jurisdictions, list_asset_coverage), sanctions (get_sanctions, check_offshore_exposure), plus payment flow (get_pricing, buy_dossier, claim_dossier, get_payment_link). Missing perhaps a 'get_relationships' separate tool but get_entity includes direct relationships. Also no explicit 'list_entities' but search covers it. Minor gaps like no bulk operations besides resolve.

Resources