website-search

get_article

Read-onlyIdempotent

Get the full content of a specific article from Lenny Zeltser's Website by URL path. Security articles on malware analysis, incident response, and security leadership. Returns title, date, topics, summary, and full body text.

Input Schema

Name	Required	Description	Default
`url`	Yes	Article URL path or full URL (e.g., '/about', '/article-slug', or the full URL printed by search results)

Output Schema

Name	Required	Description	Default
`url`	Yes
`body`	No
`date`	No
`site`	Yes
`title`	Yes
`topics`	No
`abstract`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026
- addedInput schema / properties / url / maxLength
```
Added value: +2048
```

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / url / description

Previous value: -"Article URL path (e.g., '/about', '/article-slug')"New value: +"Article URL path or full URL (e.g., '/about', '/article-slug', or the full URL printed by search results)"

Changed1 schema field changedApr 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "abstract": {
+      "type": "string"
+    },
+    "body": {
+      "type": "string"
+    },
+    "date": {
+      "type": "string"
+    },
+    "site": {
+      "additionalProperties": false,
+      "properties": {
+        "domain": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "name": {
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "domain"
+      ],
+      "type": "object"
+    },
+    "title": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "topics": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "url": {
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "title",
+    "site"
+  ],
+  "type": "object"
+}

First observedJan 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered. The description adds only that this returns the complete body text rather than an excerpt, which is useful but thin; no error behavior for a bad path or rate limits are mentioned.

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 the action and source, then the returned fields. The return-value sentence partially duplicates the output schema but remains compact and useful.

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?

A single-parameter read tool with full annotation coverage and an existing output schema needs little more; the description confirms scope and return content. Only the failure mode for an invalid or stale path is unaddressed.

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%, and the schema already documents that the url field accepts either a path or a full URL with examples. The description adds no syntax, normalization, or fallback guidance beyond what the schema states, so baseline 3 applies.

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?

States a specific verb and resource ('Get the full content of a specific article') plus the source site, and the URL-path framing implies it complements search_zeltser. It stops short of naming that sibling as the retrieval route, so differentiation is implicit rather than explicit.

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?

Usage is implied: the phrase 'the full URL printed by search results' hints that this follows a search_zeltser call. There is no explicit when-to-use versus when-not, and no statement of what to do if the path is unknown.

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

All website-search 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?