Skip to main content
Glama

ukpolice

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)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. Added

TDQS

A4.5/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, and the description adds context about scoping to the agent's identifier (anonymous IP, BYO key hash, or account ID). It also explains the list behavior when omitting the key. No contradictions, and the added scoping detail goes beyond 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 compact and front-loaded with the core action. Each sentence contributes value: the main purpose, usage examples, scoping, and related tools. No fluff or 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 memory-retrieval tool with good annotations and clear scoping, the description is sufficiently complete. It covers the main actions, usage context, scoping, and related tools. No output schema is needed since the output is the saved value or key list, and the behavior is straightforward.

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?

The schema already covers the single parameter 'key' with the description 'Memory key to retrieve (omit to list all keys)', and schema coverage is 100%. The tool description mostly repeats this information, though it adds that values were 'previously saved via remember', which provides minor additional context but does not significantly elevate 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 tool retrieves a saved value or lists keys, using specific verbs ('retrieve', 'list') and resource ('value previously saved via remember'). It also distinguishes itself from the sibling tools remember and forget by explicitly referencing them.

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 provides explicit guidance on when to use the tool ('Use to look up context the agent stored earlier...') and even gives examples (ticker, address, research notes). It also mentions pairing with remember and forget, offering clear alternative tool relationships.

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

All ukpolice 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

Several clusters of tools overlap heavily: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research all answer questions, and the five polymarket_* tools require careful reading to distinguish. The three UK police tools are clear, but they sit among many near-duplicate data-query and memory utilities.

Naming Consistency2/5

Mixed conventions: snake_case verb_noun (get_crimes) coexists with brand-style names (ask_pipeworx), noun phrases (polymarket_arbitrage), and bare verbs (forget, recall). The polymarket_* and ask_pipeworx_* families are internally consistent, but the overall set lacks a single pattern.

Tool Count2/5

34 tools is heavy, and only three relate to the server's stated ukpolice domain, while the rest form a general-purpose data platform. Many meta-tools (suggest_questions, discover_tools, pipeworx_feedback, pipeworx_trending, memory) add bulk relative to the core purpose.

Completeness3/5

For the actual Pipeworx scope, coverage is strong: query, research, comparisons, subscriptions, memory, and feedback are all present. But for the ukpolice name, it is missing many UK police endpoints (neighborhoods, stop-and-search, etc.) and has no write/update operations, so the surface feels mismatched.

Resources