Vibes-Coded Agent Tools

vc_page_markdown

Read-onlyIdempotent

Fetch a public webpage and return clean markdown plus extracted text.

Use when you already have a URL and need readable page content for an LLM.
Do not use for search discovery — call vc_web_search first.
Not for authenticated or paywalled pages.

Auth: free-trial or X-Vibes-Key preferred; else x402 (~$0.02).
Side effects: outbound HTTP GET to the URL; no local writes.
Returns JSON with markdown/text fields, or payment_required.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public https URL to fetch and convert.
`payment_signature`	No	Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds genuinely new behavioral context: an outbound HTTP GET, auth options, approximate cost, and the payment_required return case. It does not contradict the annotations and gives the agent a fuller operational picture.

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?

The description is compact, front-loaded with the core behavior, and uses short labeled lines for context. No sentence is filler; each adds either usage, exclusion, auth, side-effect, or return information.

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 two-parameter tool with a rich output schema and annotations, the description covers use case, exclusions, auth, side effects, and failure mode. An agent has everything needed to decide when to invoke it and what to expect.

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%, and the parameters have explanatory descriptions in the schema, so the description need not repeat them. The main description adds only the URL/public-page framing, which is already covered by 'Public https URL'; it does not materially enhance parameter semantics beyond the schema.

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 states a specific verb and resource: 'Fetch a public webpage and return clean markdown plus extracted text.' It also differentiates from vc_web_search by saying 'Do not use for search discovery,' so an agent can distinguish it from the closest sibling.

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?

It gives an explicit condition for use ('when you already have a URL and need readable page content for an LLM') and explicit exclusions: not for search discovery (call vc_web_search first), and not for authenticated or paywalled pages.

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

All Vibes-Coded Agent Tools tools Inspect

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.