Skip to main content
Glama

Arcgis Marioncountyor

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description goes beyond this by detailing multi-source fan-out (SEC EDGAR, GDELT/GNews, USPTO), specific failure modes (rate limits, 5xx, PatentsView sunset), and return structure (changes[] grouped by source, total_changes, pipeworx:// URIs). 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.

Conciseness5/5

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

Dense but efficiently organized; open with user-intent phrases, then logical progression through sources, fallbacks, date formats, and return value summary. Every sentence provides essential information, no filler. Completeness within a compact paragraph.

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?

Given the tool's complexity (multiple upstream APIs, fallbacks, temporal parsing) and absence of output schema, the description fully covers expected inputs, behavioral nuances (including soft-failure), and output shape. It also names the alternative tool for static profiles, making it self-sufficient for agent decision-making.

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 coverage is 100% with descriptions for all three parameters. The description adds practical meaning not in schema: examples for `since` ('7d', '30d', '3m', '1y'), recommended value ('Use "30d" or "1m"'), and `value` accepts ticker or CIK. This enriches parameter understanding beyond the schema baseline.

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 identifies the tool as a change feed for a company over a time window, with specific verb 'returns structured changes[]' and differentiates from entity_profile by stating 'Use entity_profile instead when you want the static profile'. This distinguishes it from siblings like recent_alerts.

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 provides natural language example queries ('What's new with X', 'updates on Acme') and direct comparison to alternative tool entity_profile, stating when to use which. Also describes fallback behavior (GDELT→GNews) and date format guidance ('Use "30d" or "1m" for typical monitoring'), giving clear 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 Marioncountyor 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

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, with detailed descriptions that specify when to use each. Even overlapping functions like ask_pipeworx varieties are well-differentiated by mode (casual vs grounded vs multi-source).

Naming Consistency4/5

Most tool names follow a verb_noun snake_case pattern (e.g., query_layer, resolve_entity), but a few deviate with single-word verbs (forget, remember, recall) or noun_noun (layer_info). The pattern is mostly consistent with minor exceptions.

Tool Count3/5

With 33 tools, the count is high and borders on heavy. However, the tools span multiple domains (GIS, financial data, prediction markets, memory, subscriptions), and each serves a unique role, so the count is justifiable but could be streamlined.

Completeness4/5

The tool set covers a broad range of data access and analysis tasks relevant to the inferred domain of a multi-purpose assistant. While the ArcGIS portion is limited, the overall surface is well-populated with few obvious gaps.

Resources