Skip to main content
Glama

Arcgis Tigard

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.2/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false. The description adds context about scoping to identifier and listing behavior when key is omitted, which complements annotations without contradiction.

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?

Two sentences with no wasted words. Front-loaded with the primary action, then usage guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 clear annotations, the description covers purpose, usage, and behavior. Could mention return format but not essential.

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%, and the description repeats the listing behavior already present in the schema. It adds minimal extra meaning beyond what the schema provides.

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 verb 'retrieve' and the resource 'memory keys/values'. It distinguishes from siblings 'remember' and 'forget' by explicitly mentioning them.

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 explains when to use the tool: 'to look up context the agent stored earlier'. It also notes scope and pairing with other tools, but does not explicitly state when not to use it.

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

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

Many tools have overlapping purposes, especially the various ask_pipeworx variants and entity research tools (entity_profile, compare_entities, recent_changes). The subtle differences between ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are likely to cause agent misselection.

Naming Consistency2/5

Tool names use inconsistent patterns: snake_case (ask_pipeworx, query_layer) mixed with descriptive phrases (ai_visibility_check, generate_llms_txt) and no clear verb_noun structure. Some names are vague (process, run) though those are absent here; overall naming is arbitrary.

Tool Count2/5

34 tools is too many for an Arcgis Tigard server. The majority are generic Pipeworx data query tools (27+ tools) that have little to do with ArcGIS, making the tool count feel bloated and unfocused for the server's stated purpose.

Completeness1/5

The server severely lacks ArcGIS-specific functionality. Only three tools (search_datasets, query_layer, layer_info) are relevant to ArcGIS; the rest are unrelated Pipeworx tools. Essential ArcGIS operations like editing, analysis, or visualization are missing, making the surface incomplete.

Resources