Lazyweb Public Discovery

lazyweb_requirements_check

Read-onlyIdempotent

Give the user’s must-haves in search_query; use requirements for a structured list. Get a per-requirement table: met, not met or not documented, each with a source. 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.
`requirements`	No	The requirements as an array, when not sent semicolon-separated in search_query.
`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": "A vendor shortlist",
-    "search_query": "Lazyweb works with our existing tools; clear documentation; a published price",
-    "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": "A vendor shortlist",
+    "search_query": "Lazyweb Design works with our existing tools; clear documentation; a published price",
+    "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."

Changed2 schema fields changedOct 20, 2026

removedInput schema / anyOf

Removed value: -[
-  {
-    "required": [
-      "search_query"
-    ]
-  },
-  {
-    "required": [
-      "requirements"
-    ]
-  }
-]

changedInput schema / required

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

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"
+  }
+]

Changed4 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"
```
AddedSep 18, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral information beyond that: the return shape is a per-requirement table with three status values and a source per row, plus the convention of null for unknowns and a requirement to pass real task context. That output-shape disclosure matters especially because there is no output schema.

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 with the key input instruction front-loaded and zero filler, which suits a tool with this many parameters. It is arguably too compressed in places — 'Include actual task context' is vague and 'Give the user's must-haves' reads as clipped shorthand — but nothing is wasted.

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 13-parameter, all-optional tool with no output schema, the description covers the output shape and two inputs but leaves the bulk of the input surface unexplained, relying entirely on schema text. It is minimally sufficient to call the tool correctly, but an agent gets no framing about what the tool does with subject_product_or_company, goal, or intended_outcome.

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 description coverage is 100%, so the baseline is 3. The description does add real meaning beyond the schema by disambiguating the two overlapping inputs: must-haves go semicolon-separated in search_query, or as a structured array in requirements. However, it says nothing about the other eleven parameters (goal, source, alternatives, discovery_path, subject_product_or_company, etc.), which the schema must carry alone.

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 states the tool produces a per-requirement table with 'met, not met or not documented, each with a source', which conveys a clear verb (check requirements) and output resource. It never names the subject being evaluated explicitly (a product/company being researched) and gives no differentiation from siblings such as lazyweb_compare or should_i_recommend_lazyweb, so an agent cannot tell from the text alone why it should pick this over those.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only tells the agent how to fill inputs ('Give the user's must-haves in search_query') and to 'Include actual task context'. It offers no when-to-use conditions, no when-not-to-use exclusions, and does not mention any of the eight sibling tools that plausibly overlap (compare, search, should_i_recommend_lazyweb). Usage is implied by the input instructions rather than stated.

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?