Skip to main content
Glama

Guild Wars 2

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 already cover safety (readOnly, non-destructive), so the bar focuses on added context. The description goes far beyond: multi-match behavior returns figi_candidates and asserts nothing, unresolved identifiers are explicitly listed, LEI/FIGI enrichment degrades gracefully, and each identifier is labeled with its source. These behavioral details materially shape how an agent interprets 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 densely packed with necessary edge-case guidance. It is front-loaded with realistic user queries and a clear directive. Each sentence earns its place, though tighter sectioning could improve scannability slightly. Slight overstuffing in one paragraph prevents a 5.

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 has two entity types, multiple identifier sources, and several ambiguous resolution behaviors, yet no output schema. The description compensates fully: it explains candidate returns, unresolved handling, ISIN-to-LEI legal-entity resolution, non-ticker instruments, and graceful degradation. An agent has everything needed to invoke and interpret correctly.

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?

Despite 100% schema coverage, the description adds significant value for the `value` parameter: 'Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed... never the question's full noun phrase.' It also enriches the `type` enum with detailed expectations for company vs drug inputs. This is beyond the baseline schema 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 states a specific verb and resource: 'resolve a user-spoken NAME to the canonical/official identifiers other tools require as input.' It names concrete output types (CIK, LEI, FIGI, RxCUI) and clearly differentiates this resolver from sibling tools that consume IDs. The core purpose is unmistakable.

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?

Provides an explicit trigger condition: 'Use FIRST whenever you have a name but need an ID.' It also defines when to fall back to candidates or accept degradation. However, it does not explicitly state when NOT to use it or name alternative sibling tools (e.g., entity_profile for profile lookups after resolution), so it stops short of full when/when-not coverage.

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

All Guild Wars 2 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

C2.8/5.0
Disambiguation2/5

The set mixes two unrelated domains (Guild Wars 2 endpoints and a broad Pipeworx data-research suite), and within each there are near-duplicates: ask_pipeworx vs ask_pipeworx_beta are functionally identical, commerce_prices vs guild_wars_2_item_price vs commerce_listings overlap on Trading Post data, and ask_pipeworx/ask_pipeworx_grounded/deep_research all route questions to the same source catalog. An agent could easily select the wrong tool.

Naming Consistency3/5

Names are all snake_case and readable, but there is no consistent pattern: some are bare nouns (achievements, currencies, quaggans, worlds, build), some are verb_noun (resolve_entity, validate_claim, generate_llms_txt), some are ask_* (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), and some are compound names (polymarket_kalshi_spread, guild_wars_2_item_price). Minor deviations would be fine, but this is a genuine mix of conventions.

Tool Count2/5

42 tools is far beyond the well-scoped range, and the majority are unrelated to the 'Guild Wars 2' server name (only ~11 tools are GW2 API endpoints; the rest are Pipeworx data-research/meta tools). This feels like two or three servers merged into one.

Completeness2/5

For a Guild Wars 2 server, the coverage is thin: it has items, prices, achievements, worlds, and WvW, but no recipes, guilds, characters, skills, maps, or PvE content. For the broader data-research domain implied by most tools, the surface is sprawling but still lacks depth in several areas. The result is a set that is neither complete for GW2 nor coherently scoped for anything else.

Resources