Skip to main content
Glama
dwain-barnes

MCP Server Police UK

by dwain-barnes

get_neighbourhood_boundary

Retrieve boundary coordinates for a UK neighbourhood by providing a force ID and neighbourhood ID, enabling mapping and analysis of local police areas.

Instructions

Retrieve the boundary coordinates for a specific neighbourhood

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
force_idYesThe unique identifier for the force
neighbourhood_idYesThe unique identifier for the neighbourhood

Implementation Reference

  • Schema definition for the 'get_neighbourhood_boundary' tool, defining input parameters (force_id, neighbourhood_id) and that both are required.
    {
      name: 'get_neighbourhood_boundary',
      description: 'Retrieve the boundary coordinates for a specific neighbourhood',
      inputSchema: {
        type: 'object',
        properties: {
          force_id: { type: 'string', description: 'The unique identifier for the force' },
          neighbourhood_id: { type: 'string', description: 'The unique identifier for the neighbourhood' }
        },
        required: ['force_id', 'neighbourhood_id']
      }
    },
  • Handler function for 'get_neighbourhood_boundary'. Calls the UK Police API endpoint '{force_id}/{neighbourhood_id}/boundary' and returns boundary coordinates (array).
    async function getNeighbourhoodBoundary(args: any) {
      const { force_id, neighbourhood_id } = args;
      const endpoint = `${force_id}/${neighbourhood_id}/boundary`;
      return await makeApiRequest(endpoint) || [];
    }
  • src/index.ts:460-460 (registration)
    Registration/mapping of the tool name 'get_neighbourhood_boundary' to its handler function 'getNeighbourhoodBoundary' in the toolFunctions map.
    get_neighbourhood_boundary: getNeighbourhoodBoundary,
Behavior2/5

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

No annotations provided. Description only states 'retrieve', implying read-only, but no details on side effects, data format, or limitations. Minimal behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no redundancy, front-loaded with key action. Could be longer to include context but remains direct.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should clarify return format (e.g., coordinates as polygon). Missing such details makes it incomplete for an agent to understand results.

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% for both parameters. Description adds no extra semantic value beyond the schema, which is baseline for high coverage.

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?

Description explicitly states 'Retrieve the boundary coordinates for a specific neighbourhood', with clear verb and resource. Distinct from siblings like get_neighbourhood_details or get_neighbourhoods which retrieve different data.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like locate_neighbourhood or get_neighbourhood_details. No exclusions or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dwain-barnes/police-uk-api-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server