Skip to main content
Glama
agent-reach-web-mcp

agent-reach-web-mcp

by denpadokei

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENT_REACH_MCP_TIMEOUTNoThe upstream call timeout in seconds (30 seconds by default).30

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchB

Search the web via Agent Reach (Exa semantic search, no API key required).

Returns unified envelope items: title, url, published_at, author and text highlights for each result.

fetch_contentB

Read a web page as clean markdown via Agent Reach (Jina Reader, Exa fallback).

Returns one unified envelope item with title, url, published_at and text.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: `search` discovers relevant pages via semantic search, while `fetch_content` reads a single known URL as markdown. Descriptions reinforce the boundary (search returns multiple items, fetch returns one item), leaving little room for misselection.

Naming Consistency4/5

Both names are lowercase snake_case and readable, but `search` is a bare verb while `fetch_content` follows the verb_noun pattern. This is a minor deviation from a consistent scheme rather than a real inconsistency.

Tool Count4/5

Two tools sit just under the typical 3-15 range, but they map exactly to the only two things a web retrieval server needs: discover and read. Nothing appears redundant or missing at the tool-count level, though a slightly larger surface could still be justified.

Completeness4/5

The core read-the-web lifecycle (find pages, then extract their content) is fully covered with a sensible fallback path. Gaps are minor conveniences such as batch fetching, crawling/site mapping, or structured extraction, which agents can work around by issuing multiple calls.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues