Skip to main content
Glama

Arcgis Orovalley

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.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, but the description adds substantial behavioral detail: the internal cascade through multiple endpoints, graceful degradation when GLEIF/OpenFIGI are unavailable, non-assertion and returning figi_candidates on ambiguity, and explicit labeling of unresolved identifiers. This goes well beyond the annotations and informs the agent about side-effect-free yet multi-step resolution.

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 well front-loaded with illustrative queries and the primary rule, and it is organized with SUPPORTED TYPES and enrichment sections. It is long, but nearly every sentence adds useful behavioral or semantic detail. Some repetition exists among the example phrasings, which slightly reduces conciseness.

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 having no output schema, the description covers the return behavior sufficiently: which identifiers are returned, how unresolved items are reported, what happens on ambiguous matches, and what to expect during upstream outages. For a complex entity-resolution tool with two parameters, this is complete enough for an agent 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%, so baseline is 3, but the description adds high-value semantics for both parameters. It explains the type enum in depth, including behavior per type, and gives critical value-format guidance for bonds (exact issuer string, not the noun phrase). This is essential information that the schema description alone does not convey.

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?

Purpose is explicitly stated: resolve a user-spoken name to canonical/official identifiers that other tools require. Multiple example phrasings make the intent unmistakable, and the opening line "resolve a user-spoken NAME to the canonical/official identifiers" is specific about the verb and resource. The tool is clearly distinguishable from siblings like entity_profile, which likely consumes the identifiers produced here.

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 explicitly says "Use FIRST whenever you have a name but need an ID," providing a clear trigger condition. It also explains how the tool replaces 2-3 manual lookups. However, it does not name specific sibling tools to prefer when an ID is already available, so the when-not guidance is implied rather than explicit.

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

All Arcgis Orovalley 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.9/5.0
Disambiguation3/5

The descriptions are extraordinarily detailed and genuinely differentiate most tools, but the set contains near-clones (ask_pipeworx, ask_pipeworx_beta which is explicitly 'identical' to it, and ask_pipeworx_grounded) plus five polymarket tools whose boundaries (arbitrage vs edges vs edge_tracker vs fill_risk vs kalshi_spread) overlap enough to cause misselection. An agent navigating this surface must read full descriptions to choose correctly, which defeats quick tool selection.

Naming Consistency3/5

Most tools follow a snake_case verb_noun pattern (ask_pipeworx, compare_entities, resolve_entity), but there are clear deviations: bare single-word verbs (remember, recall, forget, subscribe, unsubscribe), prefix-family names (pipeworx_feedback, pipeworx_trending; polymarket_edges, polymarket_fill_risk), and a disjoint ArcGIS trio (layer_info, query_layer, search_datasets) that breaks the dominant convention. It is readable but not predictable across the whole set.

Tool Count2/5

34 tools is far beyond what the 'Arcgis Orovalley' purpose warrants — only 3 tools (search_datasets, layer_info, query_layer) actually relate to GIS, with 31 unrelated tools bolted on covering financial data, prediction markets, memory, subscriptions, and AI visibility. This is a sprawling mega-server where an agent must hold an enormous option set in mind; the surface appears to be several platforms fused together rather than one well-scoped toolset.

Completeness3/5

The genuine ArcGIS surface (search datasets → layer_info → query_layer) is a complete read-only workflow with no dead ends, and the Pipeworx side is impressively comprehensive (routing, grounded answers, research, entity, compare, resolve, validate, memory, subscriptions, feedback). But the tool set as a whole serves no single coherent domain — the declared purpose (ArcGIS Oro Valley data) lacks any write/editing operations, while the majority of the surface addresses unrelated concerns, so 'complete' only applies to one small slice of the 34 tools.

Resources