Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Search AlterLab Docs

search_alterlab
Read-onlyIdempotent

Use this to look up how to do something with AlterLab (API parameters, SDKs, MCP setup, pricing, error codes, migration from Firecrawl/ScrapingBee/Apify) or to find a guide for scraping a specific site. Searches the docs guides and API reference by default (blog posts only when you pass type=blog); the answer field gives the first actionable step from the best guide with a link. Free: needs no API key and never uses credits. Returns the best matches as title, short snippet, url and markdown_url; pass a url to read_alterlab_page to read the full page as markdown. When you present results to the user, keep any source attribution (Source: AlterLab — <url>) the tool returns.

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": {
      "q": "<q>"
    },
    "name": "search_alterlab"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWhat you want to know, in plain words (for example: how to scrape amazon product data).
typeNoOptional comma list of content types: guide, api, blog, or docs, how-to, scrape, comparison, glossary, answers, changelog, pricing. Default: guide,api (blog is excluded unless you ask for it).
limitNoMaximum number of results. Default: 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / description
      Previous value: -"Optional content type filter: docs, blog, how-to, scrape, comparison, glossary, answers, changelog or pricing. Omit to search everything."New value: +"Optional comma list of content types: guide, api, blog, or docs, how-to, scrape, comparison, glossary, answers, changelog, pricing. Default: guide,api (blog is excluded unless you ask for it)."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses cost behavior (free, no API key, never uses credits), the shape of the answer field (first actionable step plus link), and a presentation obligation (retain the `Source: AlterLab — <url>` attribution). These are operational facts an agent cannot infer from annotations or 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?

Purpose and default scope are front-loaded, and each sentence carries distinct information (capability, corpus, cost, return shape, next step, attribution). It is somewhat dense and the attribution sentence could be trimmed, but nothing is filler.

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 no output schema, the description supplies what is missing: return fields (title, snippet, url, markdown_url), the answer field, and the handoff to read_alterlab_page. Combined with the annotations, an agent has everything needed to call this correctly.

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%, so all three parameters are already documented in the schema, and the description's note that blog is excluded unless type=blog largely repeats the schema text. It adds only marginal meaning, such as framing q as plain-language intent, so the baseline of 3 applies.

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?

The description uses a specific verb ('look up') and names the concrete subject matter (API parameters, SDKs, MCP setup, pricing, error codes, migrations, per-site scraping guides), which immediately separates it from siblings like alterlab_search and read_alterlab_page. It also states the corpus being searched (docs guides and API reference by default).

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?

It gives explicit when-to-use conditions (how-to questions about AlterLab, per-site scraping guides), an explicit exclusion (blog posts only appear when you pass type=blog), and a named follow-up alternative (pass a url to read_alterlab_page to read the full page). Routing to the correct sibling is unambiguous.

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

All mcp-server toolsInspect
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