Skip to main content
Glama

Arcgis Lacounty

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when value was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. sources_used / sources_failed say which of these actually returned data for THIS company — an empty section is a real "no data", not a bug. Pass a ticker ("AAPL"), zero-padded CIK ("0000320193"), OR a company name ("Moderna") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit notes line, not a bare failure. type accepts "company" or "ticker" interchangeably — both take the same value shapes above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna") — names resolve via SEC EDGAR company-name match.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds useful behavioral context: fans out across sources, returns specific fields, patents API sunset with soft-fail, GDELT→GNews fallback. This exceeds what annotations alone provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence carries functional weight: example queries, usage guidance, data sources, return structure, limitations, and fallback behavior. It's long but efficiently organized with semicolons and no fluff.

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 no output schema, the description fully enumerates returned fields (cik, recent_filings, fundamentals, patents, news, LEI) and explains the data sources. It also notes limitations and alternatives, making the tool's behavior predictable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description repeats the input format (ticker or CIK, names not supported) but adds no additional parameter semantics 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?

The description clearly states the tool creates a 'full cross-source profile of a US public company in ONE parallel call' and lists example queries. It distinguishes itself from chaining single-source lookups and mentions sibling tools like resolve_entity for names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it ('when the user asks for a holistic view') and ALWAYS PREFER over chaining single-pack lookups. Also provides exclusion: names not supported, use resolve_entity first.

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

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

Multiple tools have overlapping purposes: ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim all handle natural-language data queries, with ask_pipeworx_beta currently identical to ask_pipeworx. discover_tools and suggest_questions both exist to help agents find tools, and the five Polymarket tools have subtle, hard-to-distinguish boundaries. Agents will frequently select the wrong tool without careful reading.

Naming Consistency4/5

Tool names are mostly lowercase snake_case with verb-noun structure (query_layer, search_datasets, resolve_entity), which is consistent and readable. However, some names break the pattern (entity_profile, layer_info, recent_changes, pipeworx_feedback) and the prefixes are not uniform. Still, the convention is predictable enough to navigate.

Tool Count2/5

34 tools is a heavy count, and the vast majority are unrelated to the server's stated 'Arcgis Lacounty' purpose. Only three tools (search_datasets, query_layer, layer_info) serve the named GIS domain, while the rest form a sprawling collection of data-lookup, prediction-market, and utility tools. This is a severe scope mismatch.

Completeness1/5

The tool surface is severely incomplete for an ArcGIS LA County server: no layer listing beyond keyword search, no metadata endpoints, no editing, no spatial operations. The broader tool set lacks a coherent domain, making coverage impossible to assess beyond noting the glaring absence of core GIS functionality.

Resources