Skip to main content
Glama

Arcgis Carlsbad

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 (idempotentHint=true, readOnlyHint=false), the description adds critical behavioral details: key-value pairs scoped by identifier, persistent memory for authenticated users, and a 24-hour retention for anonymous sessions. This enriches the agent's understanding of side effects and lifecycle.

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 compact and well-structured, starting with the core action, then usage context, then storage details, and ending with related tools. Every sentence adds value 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 save operation with only two parameters and no output schema, the description covers purpose, usage, persistence behavior, and relationships to sibling tools. No critical information is missing.

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?

Schema coverage is 100% with both 'key' and 'value' having descriptive examples. The description does not add additional parameter-specific semantics beyond what the schema already provides, so a baseline score 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 uses a specific verb ('Save') and identifies the resource ('data the agent will need to reuse later'), with clear distinction from siblings by mentioning 'Pair with recall to retrieve later, forget to delete.' It fully clarifies that this tool stores information across conversations or sessions.

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 explicitly tells when to use: 'Use when you discover something worth carrying forward...' and provides alternative tools ('recall' and 'forget') for retrieval and deletion. This gives the agent clear decision criteria.

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

All Arcgis Carlsbad 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 tools have overlapping purposes, e.g., multiple 'ask' tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) and multiple 'compare' tools (compare_entities, scan_competitor_ai_presence). Descriptions are verbose but often don't clearly distinguish when to use each, causing confusion.

Naming Consistency1/5

Naming is highly inconsistent: snake_case (ai_visibility_check), camelCase (polymarket_fill_risk), and arbitrary prefixes (scan_, generate_, etc.). No consistent verb_noun pattern; e.g., 'query_layer' vs 'search_datasets' vs 'layer_info' all involve data retrieval but use different patterns.

Tool Count2/5

33 tools is excessive for a server purportedly focused on ArcGIS Carlsbad. Many tools are unrelated (e.g., polymarket betting, npm package scanning). The core ArcGIS functionality could be covered by 3-5 tools, but the server is bloated with Pipeworx utilities.

Completeness3/5

The ArcGIS portion lacks update/delete capabilities and is limited to querying. The Pipeworx tools cover a broad range of data sources but introduce many dependencies and meta-tools, creating a cluttered surface with dead ends (e.g., tools requiring paid accounts without fallback).

Resources