Skip to main content
Glama

RZLT

Search rzlt.io

search_rzlt
Read-onlyIdempotent

Search everything on rzlt.io (services, industries, case studies and 300+ blog posts on growth, paid ads, SEO, AEO and AI marketing). Returns titles, links and short snippets. Use it for specific topics or to find RZLT’s writing on a subject.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_rzlt"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoLimit to one kind of page (default any).
queryYesWhat to look for, e.g. "AEO for B2B SaaS" or "LinkedIn ads".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description usefully adds the result shape ('titles, links and short snippets'), but says nothing about result caps, ranking or pagination behavior.

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?

Two sentences, front-loaded with what is searched, followed by what is returned and when to reach for it. The parenthetical content list is long but informative rather than padding.

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 two-parameter read-only search with full schema coverage and rich annotations needs little more; the description also covers return contents so the missing output schema is not a gap. Only a note on result limits or how type=any behaves would improve it.

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% and both parameters carry inline descriptions and an enum, so the schema does the heavy lifting. The description adds no extra meaning about the query syntax or what the 'type' filter actually scopes beyond the schema's own wording.

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 ('Search everything on rzlt.io') and enumerates the index contents (services, industries, case studies, 300+ blog posts) plus the return shape. It does not explicitly contrast with the sibling find_case_studies, which is the one overlap an agent could trip on.

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?

'Use it for specific topics or to find RZLT's writing on a subject' implies a keyword/discovery use case but gives no when-not guidance and names no alternative. Since find_case_studies exists as a sibling, the absence of routing guidance leaves the agent to infer overlap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.