Skip to main content
Glama

Arcgis Palmbeach

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (idempotent, non-destructive, readOnly=false), the description discloses critical behavior: key-value pairs scoped by identifier, persistence differences between authenticated (persistent) and anonymous (24h) sessions, and the pairing with recall/forget. This is substantial added context not present in the 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, each earning its place: purpose, usage guidance with examples, and persistence details. It is front-loaded with the core purpose and remains concise without redundancy.

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 2-parameter write operation with no output schema, the description is complete. It covers what to store, when to use it, persistence behavior, and companion tools. No additional context is needed for an agent to invoke it correctly.

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 already provides detailed descriptions for both parameters, including examples for key and value, so schema coverage is 100%. The description adds no new parameter-level semantics beyond the general context of storing reusable information. Baseline 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 'Save data the agent will need to reuse later' with scope across conversations and sessions. It distinguishes itself from siblings by explicitly pairing with recall and forget, making its purpose distinct among the many tools.

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?

It provides explicit guidance on when to use the tool: 'Use when you discover something worth carrying forward...' and gives concrete examples. It also names alternatives ('Pair with recall to retrieve later, forget to delete'), so the agent knows when to use the companion tools instead.

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

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

B3.4/5.0
Disambiguation2/5

Multiple tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer data questions, while discover_tools and suggest_questions both serve discovery. The three ArcGIS tools are distinct but are drowned out by the unrelated Pipeworx and prediction-market tools, making it hard to pick the right one.

Naming Consistency3/5

Tool names are mostly snake_case but mix verb_noun (query_layer, search_datasets, remember), noun_noun (layer_info, entity_profile), and less conventional forms (search_within, generate_llms_txt). The naming is readable and not chaotic, but there is no single consistent pattern across the set.

Tool Count1/5

34 tools is excessive for a server named 'Arcgis Palmbeach'. Only 3 tools are GIS-related (search_datasets, query_layer, layer_info); the other 31 are unrelated Pipeworx data, prediction-market, and memory utilities. The count grossly mismatches the server's apparent purpose.

Completeness1/5

For the stated ArcGIS/Palm Beach County GIS purpose, the tool surface is severely incomplete: only search, query, and layer-schema lookup exist, with no data editing, feature operations, or map-service management. While the Pipeworx domain is heavily covered, that is not what the server name promises, so the surface is a poor fit.

Resources