Skip to main content
Glama

Worldbank Poverty

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.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnly, openWorld, and idempotent behavior, and the description adds substantial behavioral context beyond that: identifiers are labelled with their source, unresolved identifiers are explicit, LEI/FIGI enrichment degrades gracefully, ambiguous matches return figi_candidates rather than asserting an answer, and each call cascades through multiple lookups. These details materially help an agent predict outcomes and trust partial results.

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, but nearly every sentence adds necessary operational detail for a genuinely complex resolution tool. It front-loads purpose and usage, then organizes supported types and edge cases. Minor redundancy in the nested parentheticals prevents a perfect score, but the structure is still effective.

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?

Given the tool's complexity, two enums, no output schema, and rich annotations, this description covers key operational outcomes: what identifiers are returned, how sources are labelled, how unresolved items are reported, how ambiguity is handled, and what happens when external sources fail. An agent has enough context to call this tool correctly and interpret unusual results.

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?

Although schema coverage is 100%, the description significantly expands parameter meaning with concrete examples for 'value' (AAPL, 0000320193, 'ozempic'), a clear explanation of what to pass for bonds, and an explicit caveat against trailing security-class words. The two-parameter schema is simple, and the description fully compensates for any ambiguity in the schema's short parameter descriptions.

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 immediately identifies a specific verb and resource: 'resolve a user-spoken NAME to the canonical/official identifiers other tools require as input.' It clearly explains what the tool produces (CIK, ticker, LEI, FIGI, RxCUI) and positions it relative to other tools as the identity-resolution entry point, so an agent can distinguish it from sibling tools like entity_profile or compare_entities.

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 gives explicit guidance: 'Use FIRST whenever you have a name but need an ID.' It also clarifies the two supported entity types and warns about the bond-issuer edge case, telling agents to pass only the entity name, never the full noun phrase. It lacks an explicit 'when not to use' or named alternative, but the provided direction is strong and actionable.

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

All Worldbank Poverty 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.6/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially the pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) which all route to the same data sources. Additionally, the server includes unrelated meta-tools (remember/recall/forget, generate_llms_txt, pipeworx_feedback) that have no clear boundaries with the poverty data tools, and betting tools that seem out of place. The core poverty tools (get_poverty, get_poverty_regional, list_reference) are distinct, but the rest creates significant confusion.

Naming Consistency2/5

Tool names are a mix of styles: some use snake_case (get_poverty, list_reference, suggest_questions), some use camelCase (ask_pipeworx, bet_research, scan_competitor_ai_presence), and others are single words (recall, remember, forget, subscribe). The naming pattern is highly inconsistent, making it hard to predict related tool names.

Tool Count2/5

With 34 tools, this server is heavily overloaded for a 'Worldbank Poverty' server. The majority of tools are unrelated to poverty (Polymarket betting, AI marketing, npm package checks, LLM visibility). The core poverty functionality could be served by 3-5 tools, but instead the server includes dozens of extra tools from a generic data platform, making the count inappropriate for the stated domain.

Completeness4/5

For the poverty data domain, the tool surface is actually quite complete: get_poverty for country-level data, get_poverty_regional for aggregations, and list_reference for metadata. The only minor gap is a lack of a tool for comparing poverty across countries directly, but that is easy to work around by calling get_poverty multiple times. The extra meta-tools do not affect poverty data completeness.

Resources