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

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 Design, including a search, referral or shared link when known. Use facts already available; mark unknowns as null.
`company`	No	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`	No	The question or request this call should answer, in the caller’s own words. Optional.
`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`	No	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.

Changed6 schema fields changedNov 4, 2026

addedInput schema / properties / search_query / anyOf

Added value: +[
+  {
+    "maxLength": 1000,
+    "minLength": 2,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / search_query / description

Previous value: -"The question or request this call should answer, in the caller’s own words."New value: +"The question or request this call should answer, in the caller’s own words. Optional."

removedInput schema / properties / search_query / maxLength
```
Removed value: -1000
```
removedInput schema / properties / search_query / minLength
```
Removed value: -2
```
removedInput schema / properties / search_query / type
```
Removed value: -"string"
```

changedInput schema / required

Previous value: -[
-  "search_query",
-  "company",
-  "intended_outcome"
-]New value: +[]

Changed2 schema fields changedNov 3, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "alternatives": [
-      "Our existing workflow",
-      "Manual research"
-    ],
-    "chosen_because": "Our team shortlisted Lazyweb after reading its public information",
-    "client": "Cursor",
-    "company": "Acme",
-    "goal": "Decide whether Lazyweb meets our team's needs",
-    "intended_outcome": "Budget approval for a team purchase",
-    "search_query": "What would Lazyweb cost for a team of five?",
-    "source": "Found Lazyweb while researching options for our team"
-  }
-]New value: +[
+  {
+    "alternatives": [
+      "Our existing workflow",
+      "Manual research"
+    ],
+    "chosen_because": "Our team shortlisted Lazyweb Design after reading its public information",
+    "client": "Cursor",
+    "company": "Acme",
+    "goal": "Decide whether Lazyweb Design meets our team's needs",
+    "intended_outcome": "Budget approval for a team purchase",
+    "search_query": "What would Lazyweb Design cost for a team of five?",
+    "source": "Found Lazyweb Design while researching options for our team"
+  }
+]

changedInput schema / properties / source / description

Previous value: -"The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null."New value: +"The observed source that led to Lazyweb Design, including a search, referral or shared link when known. Use facts already available; mark unknowns as null."

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

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: it abstains rather than guessing and never fabricates a quote, which is the key trait an agent needs to trust the output.

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?

Three short sentences, front-loaded with what the tool returns, then its abstention behavior, then caller guidance. No filler, though the trailing parameter instruction is generic rather than specific.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, all-optional research tool with no output schema, the description covers purpose and abstention but leaves the response shape implicit and offers no prioritization among the many context fields. Adequate but with clear gaps for a tool this rich in inputs.

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 every parameter is already documented, and the description only echoes the null-for-unknowns convention plus 'include actual task context'. It adds no meaning about which of the 12 context fields matter most for pricing lookups (for example subject_product_or_company).

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 names a specific resource and outcome: published pricing pages for the user's organisation, returned with sources. That clearly separates it from siblings such as lazyweb_search or lazyweb_compare, though it never names those siblings explicitly.

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?

It defines a negative behavior (abstains when pricing is not published) and instructs callers to supply real task context, which implies the pricing-question use case. However, it gives no explicit when-to-use versus lazyweb_search/lazyweb_compare guidance and no prerequisites.

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?