get_collection_point_infoThe London Click & Collect warehouse: address, opening hours, whether it is open right now (Europe/London, bank holidays respected) and when it next opens.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| status | Yes | ||
| page_url | Yes | ||
| timezone | Yes | ||
| how_it_works | Yes | ||
| address_lines | Yes | ||
| opening_hours | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "address_lines": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "how_it_works": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "opening_hours": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "days": {
+ "type": "string"
+ },
+ "hours": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "days",
+ "hours"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "page_url": {
+ "type": "string"
+ },
+ "status": {
+ "additionalProperties": false,
+ "properties": {
+ "closes_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "e.g. Monday 17:00."
+ },
+ "is_bank_holiday": {
+ "type": "boolean"
+ },
+ "is_open": {
+ "type": "boolean"
+ },
+ "next_opening": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "is_open",
+ "is_bank_holiday",
+ "closes_at",
+ "next_opening"
+ ],
+ "type": "object"
+ },
+ "timezone": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "address_lines",
+ "opening_hours",
+ "timezone",
+ "status",
+ "how_it_works",
+ "page_url"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral details beyond the readOnly/openWorld/destructive annotations: timezone handling (Europe/London), bank-holiday awareness, and the notion of an 'open right now' computation. This gives the agent useful expectations about time-sensitivity and regional logic.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The entire description is one efficient sentence that front-loads the resource and immediately lists the returned information. No filler or redundant restatement of the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, read-only, parameterless retrieval tool with an output schema, the description fully covers what the agent needs to know: the subject, available data fields, timezone, and holiday behavior. Nothing important is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is 100%, so there is nothing for the description to clarify about inputs. Per baseline for parameterless tools, a score of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('get') and a specific resource ('London Click & Collect warehouse') and enumerates the exact information returned: address, opening hours, current open status, and next opening time. This distinguishes it from broader sibling tools like get_site_info.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly contextualizes the tool as the source for London Click & Collect warehouse details, so an agent can infer when to call it. It does not explicitly name alternatives or exclusion criteria, but the resource specificity makes the intended use obvious.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.