Skip to main content
Glama
mcp-server-demo

mcp-server-demo

by mcvalosborne

Fetch page title

fetch_page_title
Read-only

Fetches an HTTP or HTTPS URL to return its page title, final URL, and status code, blocking private, loopback, and link-local hosts.

Instructions

Fetch an http or https URL and return its document title, final URL, and status code. Loopback, link-local, and private hosts are rejected, including names that resolve to those addresses. Redirects are checked the same way. The request times out, and reading stops after the title or 64 KiB.

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_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http or https URL.
timeoutMsNoAbort the request after this many milliseconds. Defaults to 8000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, and the description adds substantive behavior beyond them: SSRF protections including DNS resolution checks and re-checking on each redirect, request timeout behavior, and a read cap at the title or 64 KiB. These are exactly the operational details an agent needs to predict success and failure.

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?

Three tight sentences, front-loaded with what the tool does, then security constraints, then limits. No filler or redundant restatement of the name.

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 parameters, full schema coverage, and no output schema, the description covers what is needed: return values are enumerated and the failure/limit conditions are spelled out. Nothing an agent requires to invoke it correctly is missing.

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 (url, timeoutMs) are fully documented with defaults and bounds in the schema itself. The description adds little parameter-level meaning beyond restating that the target is an http/https URL, so the baseline 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?

States a specific verb and resource ("Fetch an http or https URL and return its document title, final URL, and status code"), naming both the input and the returned fields. The siblings (convert_units, word_count) are unrelated operations, so an agent can select this tool without ambiguity.

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?

Usage is implied by the described inputs and outputs, and the rejection rules effectively tell the agent which requests will fail (loopback, link-local, private hosts, and redirects to them). However, there is no explicit "use this when..." framing or routing to an alternative for cases like fetching full page bodies.

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