Skip to main content
Glama

ukpolice

by io.github.pipeworx-io

Get Outcomes

get_outcomes
Read-onlyIdempotent

Get outcomes for crimes at a location for a given month. Returns outcome category and date for each crime.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude of the location
lngYesLongitude of the location
dateNoMonth to query in YYYY-MM format (e.g. "2024-01"). Defaults to latest available.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesTotal number of outcomes returned
outcomesYesArray of crime outcomes at location

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of outcomes returned",
+      "type": "number"
+    },
+    "outcomes": {
+      "description": "Array of crime outcomes at location",
+      "items": {
+        "properties": {
+          "crime_category": {
+            "description": "Crime category",
+            "type": "string"
+          },
+          "crime_id": {
+            "description": "Associated crime ID",
+            "type": "number"
+          },
+          "crime_month": {
+            "description": "Month of the crime in YYYY-MM format",
+            "type": "string"
+          },
+          "outcome": {
+            "description": "Outcome category name",
+            "type": "string"
+          },
+          "outcome_date": {
+            "description": "Date of outcome",
+            "type": "string"
+          }
+        },
+        "required": [
+          "crime_id",
+          "crime_category",
+          "crime_month",
+          "outcome",
+          "outcome_date"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "outcomes"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "lat": 51.5074,
+    "lng": -0.1278
+  },
+  {
+    "date": "2023-12",
+    "lat": 52.6369,
+    "lng": -1.1398
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the response includes outcome category and date, but since an output schema exists per context signals, this is largely redundant. No extra behavioral context such as pagination, error cases, or limitations is provided.

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, front-loaded with the action, and no filler. Every word contributes to either the purpose or the return fields. This is an example of conciseness without under-specification.

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 3-parameter tool with 100% schema coverage and rich annotations, the description is nearly complete. It states the core purpose and return essence, with the output schema expected to fill in details. Minor gaps remain, such as not describing error scenarios or edge cases like no-crime months.

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 descriptions cover all three parameters (lat, lng, date) with clear format and default behavior, so baseline 3 applies. The description's phrases 'at a location' and 'given month' merely restate the parameters without adding new semantics or usage details.

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 'Get outcomes for crimes at a location for a given month,' clearly identifying the verb (get), resource (outcome categories/dates), and scope. It distinguishes from the sibling get_crimes by focusing on outcomes rather than raw crime records, and explicitly specifies what is returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

No explicit when-to-use guidance or exclusions are provided. The phrase 'for a given month' implies temporal context, but there is no mention of alternatives or when to prefer this over get_crimes. Usage is implied rather than explicitly stated.

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