Skip to main content
Glama

Statcan

by io.github.pipeworx-io

Resolve Entity

resolve_entity
Read-onlyIdempotent

"What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: "company" (cross-source identity spine: 10-digit CIK + ticker + company_name from SEC EDGAR, legal-entity LEI from GLEIF with parent/ultimate-parent/children ownership when the LEI resolves, and security FIGI from OpenFIGI — by exact ticker map when a ticker is implied, and otherwise by name search, so NON-EQUITY instruments that never have a ticker (municipal and corporate bonds, notes, authority debt) DO resolve here; when a name matches more than one instrument it asserts nothing and returns figi_candidates to pick from, which is the correct answer to an issuer name that does not identify a single bond; every identifier is labelled with the source that established it, and an identifier that could NOT be resolved is stated explicitly under unresolved rather than omitted — accepts ticker, CIK, ISIN, or company name as input; an ISIN like "CH0038863350" resolves to the LEGAL ENTITY that issued the security via the GLEIF ISIN-to-LEI mapping, covering non-US issuers EDGAR cannot reach), "drug" (returns RxCUI + ingredient + brand from RxNorm + pipeworx://rxnorm/concept/{rxcui} citation; accepts brand or generic name). LEI/FIGI enrichment degrades gracefully — if GLEIF or OpenFIGI is unavailable, the EDGAR identifiers still return. Each call cascades through several lookup endpoints internally — using resolve_entity replaces 2-3 manual lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type: "company" or "drug".
valueYesFor company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., "ozempic", "metformin"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed ("NEW YORK ST DORM AUTH"), never the question's full noun phrase ("NEW YORK ST DORM AUTH revenue bonds"): the FIGI lookup matches instrument names, so trailing security-class words match nothing.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / value / description
      Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description discloses several behaviors: graceful degradation of LEI/FIGI enrichment, internal cascading of multiple lookups, assertion of nothing when ambiguous (returns `figi_candidates`), and explicit listing of unresolved identifiers under `unresolved`. These are non-obvious traits the agent needs to trust the tool's output.

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 description is long and dense, but every detail earns its place given the tool's complexity. It is structured logically (purpose, types, each type's specifics, degradation), yet it could be tightened—the parenthetical about non-equity instruments is verbose. Overall, highly informative with minor redundancy.

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?

Despite the absence of an output schema, the description covers return behaviors comprehensively: it mentions `figi_candidates`, `unresolved`, source labeling, and the drug-specific return fields (RxCUI, ingredient, brand, citation). It also addresses failure modes (LEI/FIGI unavailability) and edge cases (non-US issuers), leaving little the agent must guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 100%, the description adds substantial meaning beyond it. For `value`, it warns against passing full noun phrases for bonds, explains the exact issuer formatting, and gives examples for both types. It also clarifies the `type` enum's implications, making the parameters far more usable.

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 precise purpose: resolving user-spoken names to canonical identifiers (ticker, CIK, LEI, RxCUI, etc.). It gives concrete examples and names the two supported types (company, drug), distinguishing itself as a name-to-ID utility for other tools. It is clear about the resource and the action.

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 instructs 'Use FIRST whenever you have a name but need an ID', providing strong positional guidance. It also details input constraints (pass entity name only, never the full noun phrase) and mentions it replaces multiple manual lookups, clarifying when to invoke it. It does not name alternatives, but the context and 'use first' directive suffice.

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

All Statcan 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.8/5.0
Disambiguation2/5

Several tools are near-duplicates: ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, ask_pipeworx_grounded is the same router with an extra extraction pass, and deep_research/ask_pipeworx overlap for broad questions. The prediction-market tools and the StatCan series/cube/indicator tools also have fuzzy boundaries despite their detailed descriptions.

Naming Consistency3/5

Names consistently use snake_case, but the set mixes verb-first names (resolve_entity, validate_claim, subscribe) with domain-prefixed noun-first names (statcan_*, polymarket_*, pipeworx_*) and one-off names like ai_visibility_check and generate_llms_txt. The domain prefixes help navigation, but there is no single predictable pattern and the ask_pipeworx_* suffix variants break the prefix convention.

Tool Count2/5

38 tools is well beyond the 25+ threshold, and the server named Statcan carries only 8 StatCan-specific tools alongside general Pipeworx routing, prediction-market analysis, AI visibility, dependency scanning, memory, and subscription features. This feels like several servers merged into one rather than a well-scoped StatCan interface.

Completeness4/5

Within the apparent StatCan data-access scope, the surface is solid: listing cubes, metadata, cube data, vector series, headline indicators, CSV URLs, and change detection cover the core workflows. The broader Pipeworx/analysis layers also include discovery, grounded lookups, entity resolution, validation, subscriptions, and memory, with only minor gaps like server-side StatCan search and no way to execute on prediction-market signals.

Resources