Skip to main content
Glama

RZLT

Find RZLT case studies

find_case_studies
Read-onlyIdempotent

RZLT’s results for a given industry or need, e.g. industry "B2B SaaS", "maritime", "fintech", "AI"; need "launch", "pipeline", "developer signups", "SEO". Returns published case studies (with links) and, where they match, anonymous B2B results described in words. Leave both empty for the full list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_case_studies"
  }
}

Input Schema

NameRequiredDescriptionDefault
needNoWhat they want to achieve, e.g. "product launch", "more qualified leads", "show up in ChatGPT".
industryNoThe company’s industry or market, e.g. "maritime SaaS", "fintech", "consumer app".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds return-shape detail absent from annotations: published case studies with links plus anonymous B2B results "where they match" and a full-list fallback when both filters are empty. It still says nothing about what happens when a filter yields no matches at all.

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 the purpose and followed by the empty-input rule; nothing is wasted structurally. The inline example lists are somewhat long but do real work in steering the agent toward good filter values.

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?

With only two optional parameters, no output schema, and annotations carrying the safety profile, the description covers what an agent needs: what comes back, that matches may be partial, and how to request everything. Residual gaps (empty-result behavior) are minor for a read-only lookup.

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 the baseline is 3, but the description adds retrieval semantics that are not in the schema: both fields are optional and omitting both returns the complete list, and results may include anonymous narrative matches. The value examples largely duplicate the schema's own examples, which caps it below 5.

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 a concrete resource and scope: published RZLT case studies filtered by industry or need, with links plus anonymous result narratives. It is specific enough to act on, but it never contrasts itself with the sibling search_rzlt, leaving a plausible ambiguity an agent must resolve on its own.

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?

The phrase "Leave both empty for the full list" gives one actionable usage rule for the optional filters, which is genuinely helpful. However, there is no guidance on when to choose this tool over search_rzlt or check_fit, so tool-selection context is only implied.

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.