Skip to main content
Glama

httpcat

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?

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, and the description adds substantial behavioral context: graceful degradation when GLEIF/OpenFIGI are unavailable, ambiguity handled via figi_candidates, explicit unresolved identifiers, source labeling, and ISIN-to-LEI mapping. No contradiction with annotations.

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 front-loaded with examples and the 'Use FIRST' directive. Every major section earns its place, though some parenthetical detail could be tightened without losing key behavioral context.

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?

With no output schema, the description compensates by explaining key return behavior: labeled identifiers, figi_candidates for ambiguous matches, explicit unresolved fields, RxNorm citations, and degradation behavior. Supported entity types and input expectations are covered thoroughly.

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 meaningful parameter guidance: exact accepted forms by entity type, examples for ticker, CIK, name, and drug names, plus a critical warning to pass only the issuer name for bonds and an illustrative failing example. This goes well beyond the schema.

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?

Description states a specific verb and resource: resolve a user-spoken name to canonical/official identifiers that other tools need as input. It also includes concrete examples ('What's the ticker for...', 'find the CIK for...') and distinguishes itself with 'Use FIRST whenever you have a name but need an ID.'

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?

Explicitly says to use it first whenever a name needs an ID, and notes it replaces 2-3 manual lookups. However, it does not name specific sibling tools to use instead when the user already has an ID or needs a profile, so it falls short of full when/when-not/alternatives guidance.

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

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

Several tools have overlapping or near-identical purposes, e.g., ask_pipeworx and ask_pipeworx_beta are explicitly described as currently equivalent, and polymarket_arbitrage, polymarket_edges, and bet_research all target prediction-market opportunities. Descriptions help somewhat, but boundaries remain fuzzy for agents.

Naming Consistency2/5

Tool names follow no consistent convention: some are verb-first (get_status_cat, remember), others are noun phrases (entity_profile, deep_research), and many use domain prefixes (ask_pipeworx, polymarket_*, pipeworx_feedback). While snake_case is maintained throughout, the structural pattern is mixed and unpredictable.

Tool Count2/5

At 33 tools, the server is well beyond the typical well-scoped range (3-15). The count is inflated by multiple overlapping meta-tools and unrelated utility groups (HTTP cats, Pipeworx research, prediction markets, memory, subscriptions), making the set feel bloated rather than focused.

Completeness2/5

The server name 'httpcat' implies HTTP status-cat functionality, but only 2 of 33 tools serve that purpose, leaving the named domain largely uncovered. As a general-purpose data server, the collection still has gaps (e.g., no direct trading, no general web search) and appears to be a random assortment of features rather than a coherent product.

Resources