Skip to main content
Glama
Sign In

Orivale Agent Intelligence

by io.github.tapirro
OverviewDiscussionsAdmin

orivale_clean_markdown

Read-onlyIdempotent

Extract clean RAG-ready Markdown, title & pricing entities from a public https:// web page (use orivale_youtube_transcript_hooks for video URLs).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https:// URL to extract
x402_paymentNoOptional Base64 x402 PAYMENT-SIGNATURE (Base/Solana USDC) to unlock full payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / url / maxLength
      Added value: +2048
    • addedInput schema / properties / url / minLength
      Added value: +10
    • addedInput schema / properties / url / pattern
      Added value: +"^https://[^\\s/$.?#].[^\\s]*$"
    • changedInput schema / properties / x402_payment / description
      Previous value: -"Optional Base64 x402 PAYMENT-SIGNATURE"New value: +"Optional Base64 x402 PAYMENT-SIGNATURE (Base/Solana USDC) to unlock full payload."
    • addedInput schema / properties / x402_payment / maxLength
      Added value: +8192
    • addedInput schema / properties / x402_payment / minLength
      Added value: +16
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the meaningful constraint that only public https:// pages are supported, but omits the payment-gated behavior (that the payload may be truncated unless x402 is supplied), a notable trait that only appears buried in the schema.

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?

A single front-loaded sentence with the extracted artifacts first and the sibling routing parenthetical last. Nothing is wasted and nothing important is buried.

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?

With no output schema, the description does name the returned artifacts (Markdown, title, pricing entities), which is the main thing an agent needs. It falls short on the partial-payload/payment behavior and on any indication of result size or failure modes for non-public pages.

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 url and x402_payment are already documented in structured data including the payment signature format. The description adds no additional semantics such as URL normalization, redirect handling, or what 'full payload' means compared to the truncated case.

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?

Specific verb 'Extract' plus named outputs (clean RAG-ready Markdown, title, pricing entities) and the input type (public https:// web page). It also explicitly names the sibling to use for the adjacent case (orivale_youtube_transcript_hooks for video URLs), so an agent can tell the two apart without opening either 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?

States the routing condition for the video alternative explicitly, which is exactly the kind of when-not guidance that matters here. It does not, however, say anything about when the extraction would be inappropriate (e.g., login-walled pages) or when to supply the optional payment parameter.

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

All Orivale Agent Intelligence toolsInspect
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.

Resources