Skip to main content
Glama

Arcgis Lacounty

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

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, covering the safety profile. The description adds valuable behavioral details: mark_read:true mutates read state, the feed is persistent, and the return payload includes source, citation_uri, and raw event. No contradiction.

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?

Three sentences, front-loaded with the main action, then return contents and filtering, then mark_read behavior and alternative access. Every sentence adds value with no redundancy or 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?

Combined with comprehensive annotations and full schema coverage, the description completes the picture: what is returned, how filtering works, side effects, and alternative access for non-agent use. Adequate for a read-oriented alert feed tool.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all 5 parameters. The description enriches beyond this by giving an example type ('sec_8k'), specifying ISO timestamp for 'since', and explaining the effect of mark_read. It doesn't detail limit/unread_only, but the schema covers them.

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 'Pull fired events from your subscription feed' with a specific verb and resource. It differentiates from siblings like list_subscriptions (managing subscriptions) and recent_changes (general updates) by focusing on fired alerts, and adds detail about return contents.

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 clear context:'Polls work fine' and 'the same feed is also at GET registry.pipeworx.io/alerts.json' tells the agent when to use the tool vs. an HTTP endpoint. Suggests filtering by type/since for targeted usage, though it does not explicitly name alternative tools for alert retrieval.

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