Skip to main content
Glama
Sign In

Crestway Skip Hire

by uk.co.crestwayskiphire
OverviewDiscussionsAdmin

Find a town

find_town
Read-onlyIdempotent

Find English towns that have a Crestway skip hire page, by name or postcode district. Returns up to 5 matches with their county and page URL. Use the town name with town_skip_facts.

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": {
      "query": "<query>"
    },
    "name": "find_town"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA town name, or a postcode district like SN1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds real behavioral value beyond that: the result cap of 5 and the returned fields (county and page URL), which tell the agent to expect a partial list rather than a guaranteed exact match.

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?

Three short sentences: scope first, return shape second, next-step handoff third. No filler and nothing important is buried.

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 one-parameter read-only lookup with no output schema, the description covers scope, return fields, result cap and the follow-up tool. It stops short of explaining what happens on zero matches or how name matching behaves, which is the only meaningful residual gap.

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% and the schema already spells out 'A town name, or a postcode district like SN1'. The description restates that same rule without adding matching semantics such as partial vs exact matching or how ambiguous names resolve, so baseline 3 applies.

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?

States a specific verb ('Find') and resource ('English towns that have a Crestway skip hire page'), plus the accepted lookup keys (name or postcode district). It also scopes itself against the sibling by naming the downstream tool (book_with_us), so an agent can tell this is the lookup step rather than a facts/pricing tool.

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?

Usage context is explicit: use this to resolve a town name or postcode district, then pass the resulting town name to book_with_us. There are no stated exclusions or rejected input cases (e.g., ambiguous names, towns without a page), so it falls short of a full when/when-not treatment.

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