Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Read AlterLab Page

read_alterlab_page
Read-onlyIdempotent

Use this after search_alterlab to read the full text of one AlterLab page as markdown, so you can follow the documented steps instead of guessing. Pass the url of a search result. Only pages on alterlab.io that search_alterlab can return are readable. Free: needs no API key and never uses credits. 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": {
      "url": "<url>"
    },
    "name": "read_alterlab_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAn alterlab.io page URL taken from the url field of a search_alterlab result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/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 bar is met structurally. The description adds genuinely new behavior: no API key, never consumes credits, returns markdown, and returns a source attribution string the agent must preserve. It stops short of mentioning size limits or failure behavior for unreadable URLs.

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?

Front-loaded with the action and its prerequisite, then constraints, then cost model, then output-handling obligation. Every sentence carries information, though 'so you can follow the documented steps instead of guessing' is mild motivational padding.

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 one-parameter read tool with no output schema, the description covers the trigger, the input provenance, the domain restriction, the cost model, the return format (markdown), and the attribution obligation. Nothing an agent needs in order to call it correctly is missing.

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; the description goes beyond the schema by stating where the url must come from (a search_alterlab result) and constraining it to readable alterlab.io pages, which is real validity semantics the format:uri constraint does not convey.

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 — 'read the full text of one AlterLab page as markdown' — and explicitly positions it downstream of search_alterlab, so the agent can distinguish it from the search sibling without opening the 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 explicit sequencing ('Use this after search_alterlab'), an explicit input rule ('Pass the url of a search result'), and an explicit exclusion ('Only pages on alterlab.io that search_alterlab can return are readable'). The alternative tool is named rather than implied.

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