Skip to main content
Glama

Arcgis Tallahassee

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").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Describes multi-source fan-out, fallback from GDELT to GNews, soft-fail for USPTO, and structured return with citation URIs, adding substantial context beyond the annotations which already indicate read-only, idempotent behavior.

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?

Efficiently structured with example queries upfront, clear explanation of sources, parameter details, and an alternative tool recommendation; each sentence adds value.

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 documents return values (grouped changes with count and URIs) and handles edge cases like fallback and API sunset, providing complete context for a multifaceted 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 covers all parameters with descriptions; the description adds useful usage hints for 'since' (ISO or relative) and 'value' (ticker or CIK), but the value added over schema is modest, so 4 rather than 5.

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?

Description clearly defines the tool as a change feed for a company, with specific use-case examples and explicit distinction from sibling tool entity_profile for static profiles.

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?

Provides explicit when-to-use examples and directs users to entity_profile for static profile needs, offering clear differentiation from alternatives.

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

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

Multiple tools are near-duplicates or strongly overlapping: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are only mode/version variants, and discover_tools overlaps with suggest_questions, ai_visibility_check with scan_competitor_ai_presence, and the Polymarket tools with each other. An agent would frequently need a deep read of the descriptions to know which one is truly appropriate.

Naming Consistency4/5

The naming is almost entirely snake_case and mostly follows a verb_noun or domain_noun pattern, e.g. query_layer, list_subscriptions, resolve_entity, compare_entities. Minor deviations like entity_profile, pipeworx_feedback, and polymarket_arbitrage are noun-first, but the overall pattern is still recognizable and predictable.

Tool Count2/5

34 tools for a server branded 'Arcgis Tallahassee' is far too many, especially since only a handful of them are GIS-related. The rest constitute a large general-purpose Pipeworx data platform, which at this tool count becomes unwieldy and will increase an agent's selection failure rate.

Completeness3/5

The core read-only GIS flow is covered (search_datasets → layer_info → query_layer), and the Pipeworx side is broad. However, there are notable gaps: no ArcGIS service management, no layer/feature editing, no spatial operations, and no deeper GIS functions. Because the server's stated purpose is ArcGIS-focused, the overall surface is only partially complete relative to that domain.

Resources