Skip to main content
Glama

Nyc Parks

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

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral context: scoping to agent identifier and the behavior of listing all keys when the key argument is omitted. 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?

The description is three sentences, front-loaded with the core action, and every sentence adds value. No redundant or filler content.

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, full schema, and clear annotations, the description covers retrieval behavior, scoping, and the relationship with sibling tools. No output schema is present, but for a read operation this is acceptable.

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% (the key parameter is fully described in the schema). The description adds minimal extra meaning beyond the schema, mostly restating that omitting key lists all keys. The baseline of 3 is appropriate as the description provides some context but does not significantly enhance parameter understanding.

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 action ('Retrieve a value previously saved via remember, or list all saved keys') and the resource (saved memory values). It explicitly distinguishes itself from sibling tools '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?

The description provides clear guidance on when to use the tool: to look up context stored earlier without re-deriving. It mentions scoping (anonymous IP, BYO key hash, account ID) and pairs with remember and forget. It does not explicitly state when not to use, but the context is sufficient.

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

All Nyc Parks 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
Disambiguation2/5

The ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded trio are functionally near-identical to an agent (the beta is explicitly described as currently identical to stable), and the five polymarket_* tools (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread) have heavily overlapping concerns around finding and validating prediction-market edges. The descriptions are detailed, but the boundaries require careful reading to pick correctly.

Naming Consistency4/5

All tools use snake_case and mostly follow a verb-first or noun-phrase convention, with recognizable family prefixes (ask_pipeworx_*, polymarket_*, pipeworx_*) that aid navigation. Minor deviations exist — bare nouns like categories and events, and the inconsistent verb placement in bet_research vs. validate_claim — but the overall pattern is predictable.

Tool Count1/5

33 tools is already heavy, but the fatal problem is that the server is named 'Nyc Parks' while ~31 of 33 tools are a generic Pipeworx data-retrieval/prediction-market toolkit. The count is egregiously mismatched to the stated purpose; only 2 tools relate to NYC Parks at all.

Completeness2/5

For the server's literal name, the surface is severely incomplete: categories and events exist, but there is no way to look up parks, facilities, permits, or event details, and no CRUD-lifecycle coverage. Viewed as a Pipeworx data toolkit the surface is quite thorough, but that is not what the server claims to be, so the stated NYC Parks domain is barely covered and creates dead ends.

Resources