Amir Pournasserian (pournasserian.com)

Search the site

search

Read-onlyIdempotent

Searches the website Amir Pournasserian (https://pournasserian.com/): Serial entrepreneur and hands-on AI architect. I build AI and platform systems that have to keep working once they meet production, compliance and scale. Hybrid keyword and semantic search over its 86 pages, indexed on 2026-11-07; returns the best matching pages with a short snippet each. When hasMore is true, call again with offset set to the previous offset plus limit to see further results. Call fetch with a result's id or URL to read the whole page.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of pages to return, 1 to 20. Default 10.
`query`	Yes	What to look for. Natural language or keywords.
`offset`	No	Pages to skip before the first result, for paging. Default 0; values past the server's cap are clamped.

Output Schema

Name	Required	Description	Default
`query`	Yes
`total`	Yes
`hasMore`	Yes
`results`	Yes
`indexedAt`	Yes
`keywordOnly`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 24, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Pages to skip before the first result, for paging. Default 0; values past the server's cap are clamped.",
+  "type": "integer"
+}

addedOutput schema / properties / hasMore
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / indexedAt

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

addedOutput schema / properties / total
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / required

Previous value: -[
-  "query",
-  "keywordOnly",
-  "results"
-]New value: +[
+  "query",
+  "keywordOnly",
+  "indexedAt",
+  "total",
+  "hasMore",
+  "results"
+]

Changed5 schema fields changedOct 24, 2026

removedInput schema / properties / offset

Removed value: -{
-  "default": 0,
-  "description": "Pages to skip before the first result, for paging. Default 0; values past the server's cap are clamped.",
-  "type": "integer"
-}

removedOutput schema / properties / hasMore

Removed value: -{
-  "type": "boolean"
-}

removedOutput schema / properties / indexedAt

Removed value: -{
-  "format": "date-time",
-  "type": "string"
-}

removedOutput schema / properties / total

Removed value: -{
-  "type": "integer"
-}

changedOutput schema / required

Previous value: -[
-  "query",
-  "keywordOnly",
-  "indexedAt",
-  "total",
-  "hasMore",
-  "results"
-]New value: +[
+  "query",
+  "keywordOnly",
+  "results"
+]

Changed5 schema fields changedOct 24, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Pages to skip before the first result, for paging. Default 0; values past the server's cap are clamped.",
+  "type": "integer"
+}

addedOutput schema / properties / hasMore
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / indexedAt

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

addedOutput schema / properties / total
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / required

Previous value: -[
-  "query",
-  "keywordOnly",
-  "results"
-]New value: +[
+  "query",
+  "keywordOnly",
+  "indexedAt",
+  "total",
+  "hasMore",
+  "results"
+]

First observedOct 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the safety profile is covered; the description still adds real context beyond them — corpus size (86 pages), index freshness date, hybrid keyword/semantic ranking, and per-result short snippets. The paging contract (offset + limit arithmetic on hasMore) is genuinely behavioral detail not present in the annotations. It falls short of a 5 only because it says nothing about ranking quality or truncation beyond snippets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operational content is front-loaded and tight, but the second and third sentences are marketing bio ("Serial entrepreneur and hands-on AI architect. I build AI and platform systems...") that does nothing to help an agent invoke the tool. Roughly a quarter of the text is off-topic and could be deleted without loss.

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

Completeness5/5

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

For a three-parameter search tool with an output schema, this covers everything an agent needs: what is searched, how results are ranked, what each result contains, how to page, and how to escalate to fetch. Return-value detail is correctly left to the output schema rather than duplicated in prose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so limit/query/offset are already documented and the baseline is 3. The description adds meaning on top by explaining the offset/limit relationship as a paging formula tied to hasMore, which the schema alone does not express. That is a meaningful increment over the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Searches the website") plus the corpus and mechanism ("Hybrid keyword and semantic search over its 86 pages"). It also explicitly separates itself from its only sibling: "Call fetch with a result's id or URL to read the whole page." An agent can pick between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit conditional next step for paging: "When hasMore is true, call again with offset set to the previous offset plus limit." It also names the alternative tool and the exact condition that selects it (reading a full page via fetch with an id or URL). Nothing about when to use which tool is left to inference.

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

All Amir Pournasserian (pournasserian.com) 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.

Search the site

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources