Skip to main content
Glama

Arcgis Tigard

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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds that the feed is persisted, returns specific fields, and supports mark_read. No contradictions.

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?

The description is concise, front-loaded with the core action, and every sentence adds value. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without an output schema, the description covers return fields and usage scenarios. It addresses filtering and read tracking. Minor gaps (e.g., pagination, error handling) are acceptable for a simple list tool.

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 provides example values for type and since, and explains mark_read's effect, adding moderate value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 specific verb and resource. It does not explicitly differentiate from siblings, but the purpose is unambiguous and distinct from other tools.

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 explains how to filter by type and since, and how to use mark_read to track read status. It also mentions polling works and provides an alternative endpoint for scripts, offering good usage context.

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

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

Many tools have overlapping purposes, especially the various ask_pipeworx variants and entity research tools (entity_profile, compare_entities, recent_changes). The subtle differences between ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are likely to cause agent misselection.

Naming Consistency2/5

Tool names use inconsistent patterns: snake_case (ask_pipeworx, query_layer) mixed with descriptive phrases (ai_visibility_check, generate_llms_txt) and no clear verb_noun structure. Some names are vague (process, run) though those are absent here; overall naming is arbitrary.

Tool Count2/5

34 tools is too many for an Arcgis Tigard server. The majority are generic Pipeworx data query tools (27+ tools) that have little to do with ArcGIS, making the tool count feel bloated and unfocused for the server's stated purpose.

Completeness1/5

The server severely lacks ArcGIS-specific functionality. Only three tools (search_datasets, query_layer, layer_info) are relevant to ArcGIS; the rest are unrelated Pipeworx tools. Essential ArcGIS operations like editing, analysis, or visualization are missing, making the surface incomplete.

Resources