Skip to main content
Glama

Arcgis Sanjose

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 already declare readOnlyHint=true and destructiveHint=false; description adds important scoping info (scoped to identifier: anonymous IP, BYO key hash, account ID). Notes that it avoids re-deriving info. 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?

Four sentences, each serving a distinct purpose: core function, use case, scoping, related tools. Front-loaded with primary action. No extraneous content.

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?

Covers retrieval behavior, dual mode, and scoping. Lacks details on error handling or return format, but for a simple retrieval tool with good annotations, this is reasonably complete.

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% (parameter 'key' documented). Description reiterates that omitting key lists all keys, which adds marginal value. The examples in the input schema also help. 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?

Explicitly states the verb 'retrieve' and resource 'value saved via remember'. Distinguishes between retrieving a specific key and listing all keys. Provides concrete examples of stored context (ticker, address, notes), and implicitly differentiates from siblings '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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly states when to use: to look up previously stored context. Covers both usage modes (with or without key). Mentions pairing with remember/forget, giving context on lifecycle. Does not explicitly state when not to use, but for a straightforward retrieval tool this is sufficient.

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

All Arcgis Sanjose 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.8/5.0
Disambiguation3/5

While many tools have distinct purposes, there is overlap between ask_pipeworx, ask_pipeworx_grounded, and deep_research, as well as multiple Polymarket and entity-related tools. Descriptions are detailed but could confuse agents on which tool to use for a specific query.

Naming Consistency3/5

Most tool names use snake_case and many start with verbs, but there is inconsistency with noun-starting names like entity_profile, layer_info, and pipeworx_feedback. No strong verb_noun or other consistent pattern across the set.

Tool Count3/5

With 33 tools, the count is relatively high but could be justified for a broad data platform. However, given the server name 'Arcgis Sanjose', the number seems excessive as most tools are unrelated to ArcGIS geospatial functions.

Completeness2/5

The tool set is severely incomplete for the implied ArcGIS San Jose domain, with only 3 tools (search_datasets, layer_info, query_layer) supporting that purpose. The rest are from the Pipeworx ecosystem, creating a mismatch between server name and actual functionality.

Resources