Skip to main content
Glama
Node Mantis

Node Mantis

Official

Read data from a page

retrieve_data
Read-onlyIdempotent

Reads data from a single web page without altering it, returning structured output when a result schema is supplied. Use it when no clicking, typing or multi-page navigation is needed.

Instructions

Open one page and read data from it without changing anything on it. Returns the data, shaped by result_schema when given. Use run_task instead when getting to the data takes clicking, typing or several pages. If reading is still going when the call returns, the reply has status "running" and a task_id: call get_task with it.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe page to read (http or https).
effortNoHow much capability to spend. Default medium; raise it for hard pages, lower it for simple ones.
promptYesWhat to read from the page, e.g. "every listing with its title, price and link".
use_proxyNoRoute the browser through the proxy configured in this server's environment. Default false.
show_browserNoShow the browser window while the task runs. Default false unless the server was started with --headed.
result_schemaNoJSON Schema describing the shape of the data to return, for example {"type":"object","properties":{"price":{"type":"number"}},"required":["price"]}. Omit it for a free-form answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.9

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint/openWorldHint annotations, the description discloses the async completion protocol that annotations cannot express: a partial read returns status "running" with a task_id that must be handed to get_task. It also explains how result_schema shapes the returned data, which is real behavioral context rather than restated metadata.

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?

Three short sentences, front-loaded with the core action and safety guarantee, then alternatives, then the async follow-up. No filler, and each sentence carries distinct information an agent needs.

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 enough by explaining that results are shaped by result_schema and what a partial result looks like. It stops short of describing error or failure behavior and whether repeated calls on dynamic pages return consistent data, which would matter for a 6-parameter open-world fetch.

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%, so every parameter including enum values and defaults is already documented structurally. The description only reinforces result_schema's effect on output shape and does not add syntax, constraints, or interaction rules beyond the schema, so the baseline of 3 applies.

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 ("Open one page and read data from it") and adds an explicit scope constraint ("without changing anything on it"). An agent can immediately tell this is a single-page read operation, distinct from the sibling run_task.

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 names the alternative and the exact condition that selects it: "Use run_task instead when getting to the data takes clicking, typing or several pages." It also routes the async case to get_task with the concrete trigger (status "running" plus a task_id), so both branching decisions are spelled out.

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