Skip to main content
Glama

Arcgis Eagan

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context: 'Scoped to your identifier (anonymous IP, BYO key hash, or account ID)' and describes the two operational modes (retrieve by key, list all keys). No contradictions 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?

The description is three sentences long, front-loaded with the primary action, and every sentence provides essential information. There is no redundancy or filler, making it highly concise and well-structured.

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 one optional parameter and strong annotations, the description is complete. It covers purpose, usage context, scoping, and relationships to siblings. No output schema exists, but the return values are implicitly understandable from the description.

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 schema already provides a clear description for the 'key' parameter: 'Memory key to retrieve (omit to list all keys)'. The description repeats this functionality but adds no new parameter-specific semantics. Since schema coverage is 100%, the baseline of 3 is appropriate.

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's function: 'Retrieve a value previously saved via remember, or list all saved keys'. It uses specific verbs (retrieve, list) and identifies the resource (saved keys/values). It also distinguishes itself from related sibling tools by explicitly referencing 'remember' and 'forget'.

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?

The description provides explicit usage context: 'Use to look up context the agent stored earlier... without re-deriving it from scratch.' It also names alternatives and companions: 'Pair with remember to save, forget to delete.' This clearly positions the tool relative to siblings and gives concrete scenarios.

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

All Arcgis Eagan 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

Several tool groups overlap heavily: the three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) differ mainly in guarantees, and six Polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) all target the same trading-concept space with fuzzy boundaries. While ArcGIS, memory, and subscription tools are distinct, an agent will frequently struggle to pick the right research or analysis tool.

Naming Consistency2/5

All names are snake_case, but the structural pattern is inconsistent. Some are verb-first (query_layer, search_datasets, validate_claim), others are noun-first or domain-prefixed (entity_profile, layer_info, polymarket_edges, recent_alerts, pipeworx_feedback). There is no predictable verb_noun convention across the set, making it hard to guess a tool's name from its function.

Tool Count2/5

At 34 tools, the set is well above the typical focused-server range, and the server name 'Arcgis Eagan' suggests a narrow GIS purpose while only 3–4 tools are actually ArcGIS-related. The remaining ~30 tools form a broad, unrelated utility collection (Pipeworx data, memory, subscriptions, trending, npm scanning), making the count feel bloated and unfocused.

Completeness2/5

For the primary ArcGIS domain, only search, layer inspection, and querying are supported — there are no create, update, delete, or editing tools, leaving obvious lifecycle gaps. Meanwhile, the Pipeworx side is over-stocked with redundant analysis tools, and the overall mix lacks a coherent coverage story for any single stated purpose.

Resources