Skip to main content
Glama

ukpolice

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations, it discloses that memory is scoped by user identifier, and specifies persistence: authenticated users get persistent memory, anonymous sessions retain for 24 hours. This adds meaningful behavioral context (auth needs, retention) beyond structured 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 short sentences, front-loaded with purpose, then usage, then technical details. No superfluous 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?

For a simple key-value write tool, the description covers what it does, when to use it, how data is scoped, retention behavior, and related tools. No output schema is needed, so nothing essential is missing.

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 input schema already describes both parameters with examples and value type (100% coverage). The description's examples ('resolved ticker, target address, user preference') overlap with schema's examples and add no new technical constraints.

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 opens with 'Save data the agent will need to reuse later' — a specific verb+resource. It provides concrete examples and explicitly names sibling tools recall and forget, distinguishing this as the storage operation.

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 'Use when' guidance with examples of what to store, and directs pairing with recall/forget, making appropriate usage and alternatives clear.

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