Skip to main content
Glama

Route and run a request

web_run
Destructive

Route plain-language web requests, such as reading a URL or researching a report, to the right backends with cost and time caps; use dry_run to preview the plan without billing.

Instructions

Hand a request in plain words to web-router's router, which picks the method and backends and runs it (by default: a URL is read, a report or comparison researched -- billed, minutes long, so set max_cost_usd -- anything else searched). Call a tool directly for its options. dry_run=true returns the plan and bills nothing.

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": {
      "prompt": "<prompt>"
    },
    "name": "web_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesWhat to find or read, in words; a URL in it is read as one to fetch.
dry_runNoReturn the plan -- method, options, backend order, decision record -- without running it.
max_cost_usdNoCaps this call, within the session's budget, in US dollars.
time_limit_sNoCaps this call's wait, within the session's budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.5/5.0
Behavior4/5

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

The description adds real behavioral context beyond the annotations: calls are billed, take minutes, and should be cost-capped, and dry_run=true returns the plan without billing. It is consistent with destructiveHint=true / openWorldHint=true rather than contradicting them. It stops short of saying what a real run actually returns or what failure modes look like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and no filler sentences. The nested parenthetical with em-dashes packs the routing defaults and billing warning into one dense clause, which is efficient but slightly harder to parse than separate sentences.

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?

Given no output schema, the description covers the important pre-call decisions: routing behavior, cost, latency, and the dry-run planning mode. A brief note on what a real (non-dry-run) run returns would close the remaining gap for this open-world, billed tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by explaining why max_cost_usd matters (billed, minutes-long) and that dry_run both returns the plan and bills nothing, which the schema fields alone do not convey. time_limit_s is left to the schema but that is acceptable at full coverage.

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 action and resource: it hands a plain-words request to web-router's router, which selects the method and backends and runs it. It also enumerates the default routing outcomes (URL read, report/comparison researched, anything else searched), which lets an agent distinguish this from calling a specific tool like browse or research directly.

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?

Explicitly says when to use it (an unclassified plain-words request) and when not to ("Call a tool directly for its options"), and adds the cost condition that should trigger setting max_cost_usd. The dry_run escape hatch is named with its consequence.

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