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 / properties / status / properties / closes_at / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / status / properties / closes_at / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / status / properties / next_opening / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / status / properties / next_opening / typeAdded value: +[
+ "string",
+ "null"
+]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 annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds meaningful behavioral context beyond the annotations: the open status is evaluated in Europe/London time and respects bank holidays, which tells the agent this is a time-sensitive lookup rather than a static record.
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 definition is a single dense sentence with the resource front-loaded and every clause contributing useful information about the returned data. There is no redundant explanation or repetition of structured fields.
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 zero-parameter read-only tool with an output schema and clear annotations, the description supplies all the context an agent needs: what location is covered, what fields are returned, and how open status is computed. Nothing essential is missing for correct invocation.
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?
There are zero parameters, so parameter semantics carry no burden and the baseline is 4. The description appropriately does not invent parameter details for a no-argument tool.
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 names a specific resource (the London Click & Collect warehouse) and enumerates the exact information returned: address, opening hours, current open status, and next opening time. It is immediately clear what the tool does and there is no sibling tool for collection point information, so no further differentiation is needed.
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?
Usage is implied by the resource name and listed fields, but the description gives no explicit when-to-use guidance, prerequisites, or alternative tools to consider. An agent can infer it should call this when collection point details are needed, but the definition does not actively route between this and related tools like estimate_delivery or check_shipping_availability.
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.