Skip to main content
Glama

Arcgis Delawareco

by io.github.pipeworx-io

Generate llms.txt

generate_llms_txt
Read-onlyIdempotent

Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull URL of the site to summarize, e.g. "https://example.com" or a specific landing page.
max_linksNoMaximum number of link entries to include (default 25, max 50).

TDQS

A4.3/5.0
Behavior4/5

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

The description explains the internal process (fetches the page, extracts title/description/key links, emits standard markdown) and output format, adding value beyond the readOnlyHint/idempotent annotations. It doesn't cover error handling, but the annotations already establish safety, so this is sufficient.

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 three sentences: purpose, process/output, and use cases. Every sentence adds value, and the most important information is front-loaded. No redundant or verbose phrasing.

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?

For a simple tool with two well-described parameters, no output schema, and strong annotations, the description fully covers what, how, and when. It gives enough behavioral detail to invoke correctly without over-explaining.

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?

The input schema covers both parameters with full descriptions (url and max_links with default/max), so the description doesn't need to add much. It implicitly clarifies the output is a text blob but doesn't elaborate on parameter formats beyond the schema, matching the baseline for high schema coverage.

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 generates a production-ready llms.txt file for any URL, with a specific verb ('Generate'), resource ('llms.txt file'), and scope ('for any URL'). It also defines the output as a single text blob, making its purpose unambiguous and distinct from sibling 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 includes explicit use cases: getting a client's site indexed, drafting llms.txt for a project, and auditing a competitor's AI visibility. While it doesn't mention alternatives or exclusions, the context is clear enough to guide when to use this tool.

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

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

Many tools have overlapping or redundant purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical in routing, and several polymarket tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk) all surface trading opportunities with similar outputs. The three ArcGIS tools are distinct but buried among dozens of unrelated data/meta tools, making selection confusing.

Naming Consistency3/5

All names use snake_case, which is consistent, but the verb/noun pattern is inconsistent. Some are verb_noun (query_layer, resolve_entity), some are noun phrases (entity_profile, polymarket_edges, recent_alerts), and some are bare verbs (recall, remember, forget, subscribe). The naming style is readable but not predictably patterned.

Tool Count1/5

34 tools is already high, but the severe issue is that only 3 of them (search_datasets, query_layer, layer_info) relate to the server's stated ArcGIS Delaware County purpose. The other 31 are Pipeworx data, memory, subscription, and prediction-market tools, which is a blatant scope mismatch. The tool count is not appropriate for the advertised server domain.

Completeness1/5

For an ArcGIS Delaware County GIS server, the surface is extremely thin: only search, query, and layer metadata exist. There are no tools for editing features, uploading data, managing layers, or exporting maps. Conversely, the Pipeworx tools form a broad but fragmented domain with many monitoring and meta-tools but no clear end-to-end workflow. The set is severely incomplete for its apparent dual purpose.

Resources