Skip to main content
Glama
Sign In
veris

veris

by jakeyoung1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Web Read (provenance-tracked)

web_read

Fetch a URL and return clean markdown with verifiable source metadata: published date, author, canonical URL, content hash, fetch time, and license signals.

Instructions

Fetch a URL and return clean markdown PLUS provenance: published date, author, canonical URL, content hash, fetch time, and license signals. The provenance is the point — verifiable source metadata an AI normally cannot get.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL to read
freshNoBypass cache and refetch (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations available, the description carries the burden. It discloses the output (clean markdown plus provenance details) and the core value, but does not address error behavior, redirects, rate limits, or limitations. It is adequate but not deeply transparent.

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, front-loaded with the main action, and each word adds value. No fluff.

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 tool with two parameters, no output schema, and no annotations, the description covers the core functionality and unique value proposition well. It could be slightly more complete by noting error scenarios or typical use cases, but it is largely sufficient.

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% for both parameters (url and fresh). The description adds no new parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 the specific verb 'Fetch' with a clear resource ('a URL') and emphasizes the provenance-tracking distinction, which sets it apart from siblings like web_search and web_research.

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?

The context is clear: use when you have a URL and want clean markdown with verifiable provenance. It doesn't explicitly mention alternatives, but the purpose is unambiguous. No exclusions are stated.

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