Skip to main content
Glama
Sign In

Ukpolice

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Forces

get_forces
Read-onlyIdempotent

List all police forces in England, Wales, and Northern Ireland. Returns force ID and name.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYesTotal number of police forces
forcesYesArray of police forces

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of police forces",
+      "type": "number"
+    },
+    "forces": {
+      "description": "Array of police forces",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Force ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Force name",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "forces"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  3. First observed

TDQS

A3.9/5.0
Behavior1/5

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

The description claims to list 'all' police forces, which contradicts the annotation openWorldHint=true, indicating the tool may not return a complete/closed-world set. This is an annotation contradiction, leading to the score of 1.

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 entire description is one concise, front-loaded sentence that specifies action, scope, and return fields. Every word earns its place, with no 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 parameterless list tool with an output schema and comprehensive annotations, the description provides all necessary contextual information (geographic scope, return content). The contradiction with openWorldHint is a transparency issue already scored, but contextually the description is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the baseline is 4. The description adds no parameter-specific meaning since none exists, and the schema confirms this. No further compensation is needed.

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's action ('List all police forces'), scope ('England, Wales, and Northern Ireland'), and return fields ('force ID and name'). This distinguishes it from siblings like get_crimes and get_outcomes, which focus on crime data.

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 implies clear usage: whenever a list of police forces is needed, likely as reference data for other tools. However, it does not explicitly mention alternatives or exclusionary conditions. Given the tool's simplicity and zero parameters, the context is sufficiently 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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources