Skip to main content
Glama
Sign In
yeivily-mcp

yeivily-mcp

by yeib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fetch_page

Read-onlyIdempotent

Download a single web page and return readable text to read a URL found via web search. It does not run JavaScript or read PDFs.

Instructions

Download a single web page and return its readable text. Use it to read a URL found via web_search. Does not execute JavaScript and does not read PDFs.

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": "fetch_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttp(s) URL to read.
max_charsNoMaximum characters of text to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds behavioral boundaries the annotations do not convey: no JavaScript execution and no PDF support, which materially affect whether a fetch will succeed. It stops short of describing failure modes, redirects, or authentication requirements.

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

Conciseness5/5

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

Two sentences with zero filler, and the core action plus output are front-loaded ahead of the usage hint and limitations. Every clause carries information the agent needs.

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?

For a simple two-parameter read tool with full schema coverage and an existing annotation set, this description covers purpose, usage, output type, and key limitations. Only minor operational details such as error or truncation behavior are absent, and there is no output schema requiring explanation.

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 description coverage is 100%, so both the URL format and max_chars default are already documented in the schema. The description adds no syntax, format, or truncation semantics beyond that baseline, so it warrants the standard 3 rather than more.

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 names a specific verb and resource ("Download a single web page") and states the concrete output ("readable text"). It also distinguishes the tool from adjacent capabilities by ruling out JavaScript execution and PDF reading, so an agent can tell what this does 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 Guidelines4/5

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

It gives explicit usage context: "Use it to read a URL found via web_search," naming the sibling and the workflow that selects this tool. The exclusions for JavaScript-heavy pages and PDFs further narrow applicability, though it does not say what to do instead in those cases.

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

Deploy Server

Other Tools