Skip to main content
Glama

Arcgis Roanoke

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
Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, and the description adds valuable context about scoping: 'Scoped to your identifier (anonymous IP, BYO key hash, or account ID)'. This goes beyond the annotations, though it doesn't cover error cases or return format details.

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 two sentences, front-loaded with the main action, and every phrase adds value: it covers behavior, examples, scoping, and related tools without wordiness.

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?

Given the tool's simplicity (1 optional parameter, no output schema), the description is complete: it explains the return behavior (value or list of keys), the scoping, and how it relates to remember/forget. Annotations cover safety, so no gap remains.

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?

The schema covers 100% of parameters with descriptions, so baseline is 3. The description adds semantic context by explaining that omitting the key lists all keys and that keys refer to values 'previously saved via remember', which reinforces the schema meaning.

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 identifies a specific verb and resource, and distinguishes itself from siblings 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?

It provides explicit usage context: 'Use to look up context the agent stored earlier' and gives concrete examples. It also names the companion tools for saving and deleting, giving clear when-to-use and alternatives.

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

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

The tools span vastly different domains (AI visibility, data querying, prediction markets, GIS) with clear descriptions individually, but the set lacks a coherent focus. An agent looking for ArcGIS functionality would be distracted by many unrelated tools, causing confusion in tool selection.

Naming Consistency2/5

Most tool names use snake_case, but there is no consistent verb_noun pattern. Some names are verbs (remember, forget), others are noun phrases (entity_profile, layer_info), and some include underscores inconsistently (generate_llms_txt vs. bet_research). The naming feels arbitrary.

Tool Count1/5

With 33 tools, the count is high, but the vast majority are from Pipeworx and unrelated to the server's stated purpose (Arcgis Roanoke). Only 3-4 tools actually relate to GIS. The tool count is extremely inappropriate for the server's focus.

Completeness1/5

For the implied domain of ArcGIS Roanoke, the tool surface is severely incomplete, lacking CRUD for map layers, spatial queries, or data management. Conversely, the Pipeworx subset is also incomplete on its own (e.g., missing many data sources). The overall surface fails to serve any single domain well.

Resources