Skip to main content
Glama
Sign In

Crestway Skip Hire

by uk.co.crestwayskiphire
OverviewDiscussionsAdmin

Skip hire prices by postcode

skip_prices
Read-onlyIdempotent

Guide skip hire prices in England for a UK postcode (full, like "SN1 2AB", or just the district, like "SN1"): the price for each skip size from 2 yard mini to 12 yard maxi, ex VAT, with the local Crestway page for that town when there is one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postcode": "<postcode>"
    },
    "name": "skip_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYesA UK postcode or postcode district

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and determinism are covered. The description adds useful context beyond that — prices are ex VAT, coverage spans the full size range, and a town page may or may not be present — but says nothing about what happens with an unrecognised postcode or how current the prices are.

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?

A single front-loaded sentence with the resource first and the return details after; every clause carries information (scope, formats, pricing basis, size range, optional town page). The lead-in 'Guide skip hire prices' is slightly clumsy phrasing for what is really a lookup.

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?

With only one parameter, full schema coverage, annotations covering the read-only profile and no output schema, the description does enough: it establishes geography, VAT basis, size range and the optional town link. Only the failure mode for an unmatched postcode is left unaddressed.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns a nudge above it by restating both accepted forms (full postcode "SN1 2AB" or district "SN1") and pinning the geographic scope to England, which the schema does not say.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource (skip hire prices for a UK postcode) and enumerates the return content — price per skip size from 2 yard mini to 12 yard maxi, ex VAT, plus the local Crestway town page. It implicitly separates itself from skip_sizes by returning prices rather than the size catalogue, but it never names that sibling outright.

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?

Usage is only implied: an agent infers it should call this when a user supplies a postcode and wants cost. There is no explicit when-to-use statement, no mention of the alternatives (skip_sizes, town_skip_facts, how_to_book), and no exclusion such as non-England postcodes.

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

All Crestway Skip Hire 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