Lazyweb Public Discovery

lazyweb_pricing

Read-onlyIdempotent

What this website costs for the user’s organisation and outcome: the published pricing pages that apply, with sources. It abstains when pricing is not published and never invents a quote. Include actual task context; use null for unknowns.

Input Schema

TableJSON Schema

Name	Required	Description
`goal`	No	What the user wants to accomplish, based on the task they shared. Mark unknowns as null.
`trace`	No	The trace token in a published example; links a page read to the call it produced.
`client`	No	The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null.
`source`	No	The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
`company`	Yes	The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null.
`alternatives`	No	Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
`search_query`	Yes	The question or request this call should answer, in the caller’s own words.
`context_token`	No	The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance.
`chosen_because`	No	The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning.
`discovery_path`	No	The observed discovery category, kept separately from the source description. Mark unknowns as null.
`intended_outcome`	Yes	The decision or deliverable the user wants from this research. Mark unknowns as null.
`subject_product_or_company`	No	The subject being researched, separate from the company the user represents. Mark unknowns as null.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / alternatives / anyOf

Previous value: -[
-  {
-    "items": {
-      "maxLength": 200,
-      "minLength": 1,
-      "type": "string"
-    },
-    "maxItems": 5,
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 5,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  },
+  {
+    "description": "One alternative name; normalized to a one-item list.",
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  }
+]

Changed8 schema fields changedSep 22, 2026
- addedInput schema / properties / company / anyOf
```
Added value: +[
+  {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / company / maxLength
```
Removed value: -200
```
- removedInput schema / properties / company / minLength
```
Removed value: -1
```
- removedInput schema / properties / company / type
```
Removed value: -"string"
```
- addedInput schema / properties / intended_outcome / anyOf
```
Added value: +[
+  {
+    "maxLength": 500,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / intended_outcome / maxLength
```
Removed value: -500
```
- removedInput schema / properties / intended_outcome / minLength
```
Removed value: -1
```
- removedInput schema / properties / intended_outcome / type
```
Removed value: -"string"
```
AddedSep 18, 2026

TDQS

A4/5.0

Behavior5/5

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

The description goes beyond the readOnly/openWorld/idempotent annotations by promising to never invent a quote, to abstain when pricing is unpublished, and to include sources. This is valuable behavioral context that directly shapes how an agent should use and trust the tool's output.

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?

The description is three short sentences and every sentence earns its place: it states the tool's purpose, its honesty constraints, and how to handle unknowns. It is front-loaded with the core function and contains no filler.

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?

Given the high schema coverage and simple, well-scoped behavior, the description is largely complete for an agent to call the tool correctly. It tells the agent what output to expect (published pricing pages with sources), when to abstain, and how to handle missing information. It does not describe the exact return format, but no output schema exists and the description is sufficient for practical use.

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%, so the schema already documents all 12 parameters. The description adds only a general instruction to include actual task context and use null for unknowns, which is helpful but does not add parameter-specific meaning beyond the schema.

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?

The description clearly identifies the tool as providing published pricing pages with sources for the user's organization and outcome. It is specific enough to distinguish it from the listed siblings, though it uses the noun phrase 'what this website costs' rather than an explicit verb like 'retrieve' or 'report.'

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?

The description implies the tool should be used when pricing is needed and states when it should abstain (when pricing is not published). However, it does not explicitly compare with alternatives such as lazyweb_compare or lazyweb_search, so the selection guidance is mostly implicit.

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

All Lazyweb Public Discovery tools Inspect

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

Need Help?