Skip to main content
Glama

recipes

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. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Entity type. v1 supports \"company\"."New value: +"Entity type: \"company\" or \"drug\"."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "drug"
+]
    • changedInput schema / properties / value / description
      Previous value: -"Ticker, CIK, or company name (e.g., \"AAPL\", \"0000320193\", \"Apple\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the hints (readOnly, idempotent, openWorld, non-destructive), the description discloses graceful degradation ('LEI/FIGI enrichment degrades gracefully'), ambiguity handling ('asserts nothing and returns figi_candidates'), and unresolved identifiers being explicit. This enriches the annotation profile and is consistent with it.

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 text is long, but every clause earns its place: query examples, supported types, sources, ambiguity behavior, failure modes, and input constraints. It could be organized more tightly, but for the tool's complexity the density is justified and the key directive ('Use FIRST...') is front-loaded.

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?

There is no output schema, yet the description covers what gets returned (CIK, ticker, LEI, FIGI, RxCUI, unresolved list, figi_candidates), the sources behind each, and when enrichment may be missing. Together with the rich annotations, an agent has enough to call and interpret results 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?

Schema coverage is 100%, but the description adds substantial meaning: it clarifies that value must be the entity name only (not the full noun phrase) and explains the bond/ISIN edge cases. It also maps type to the supported entity kinds and their output identifiers, well beyond the enum labels.

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 is anchored by a specific verb-resource pair: 'resolve a user-spoken NAME to the canonical/official identifiers,' and backs it with six concrete query phrasings. This makes the tool's unique role—name-to-ID conversion—unmistakable against siblings like entity_profile or compare_entities, so an agent can select it without opening schemas.

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?

It states the central trigger explicitly: 'Use FIRST whenever you have a name but need an ID,' and details accepted input formats (ticker, CIK, ISIN, name, brand/generic drug name). It stops short of naming when-not-to-use alternatives (e.g., after an ID is already known, use entity_profile), so the exclusion is implied rather than spelled out.

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

All recipes 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

A4/5.0
Disambiguation5/5

Each tool has a highly specific purpose with detailed descriptions, making them easily distinguishable. Overlaps are minimal; for instance, Pipeworx and Polymarket tools have distinct roles within their domains.

Naming Consistency4/5

Most tools follow a consistent snake_case pattern (e.g., ask_pipeworx, compare_entities), but a few single-word names (e.g., forget, recall) deviate slightly, causing minor inconsistency.

Tool Count2/5

The server is named 'recipes' but contains only 4 recipe-related tools out of 34. The majority cover unrelated domains like finance, betting, and data queries, making the scope overly broad and misaligned with the server name.

Completeness2/5

For the 'recipes' domain, essential CRUD operations and features like meal planning are missing. While the general tool set is extensive, it lacks critical recipe-related functionality, leaving significant gaps for the intended purpose.

Resources