oassis — web scraping, crawling and browser control for AI agents

web_map

Read-onlyIdempotent

Every url of a site, fast and cheap: its sitemap plus, optionally, the links on the page. Use it BEFORE crawling, to see what is there and decide what is worth reading. 1 credit ($0.002) with includePage: false (no browser at all), 1.5 credits ($0.003) with the page. Reference for the oassis API: https://oassis.dev/openapi.json

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Page to process.
`limit`	No	Urls to return. Up to 5000.
`search`	No	Keep only urls containing this text.
`includePage`	No	Render the page too, to catch urls the sitemap does not list. `false` uses no browser at all, so it costs less: $0.002 against $0.003.
`excludePaths`	No	Discard urls whose path contains one of these. Up to twenty. It wins over `includePaths`.
`includePaths`	No	Keep only urls whose path contains one of these. Up to twenty.
`includeSubdomains`	No	Treat subdomains of the same site as part of it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / includePage / description

Previous value: -"Render the page too, to catch urls the sitemap does not list. `false` uses no browser at all, so it costs less: $0.001 against $0.0015."New value: +"Render the page too, to catch urls the sitemap does not list. `false` uses no browser at all, so it costs less: $0.002 against $0.003."

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / includePage / description

Previous value: -"Render the page too, to catch urls the sitemap does not list. `false` uses no browser at all and costs a third."New value: +"Render the page too, to catch urls the sitemap does not list. `false` uses no browser at all, so it costs less: $0.001 against $0.0015."

Changed17 schema fields changedOct 4, 2026
- addedInput schema / properties / excludePaths / description
```
Added value: +"Discard urls whose path contains one of these. Up to twenty. It wins over `includePaths`."
```
- addedInput schema / properties / excludePaths / items / minLength
```
Added value: +1
```
- addedInput schema / properties / excludePaths / maxItems
```
Added value: +20
```
- changedInput schema / properties / includePage / description
```
Previous value: -"Render the page too (default true)."New value: +"Render the page too, to catch urls the sitemap does not list. `false` uses no browser at all and costs a third."
```
- addedInput schema / properties / includePaths / description
```
Added value: +"Keep only urls whose path contains one of these. Up to twenty."
```
- addedInput schema / properties / includePaths / items / minLength
```
Added value: +1
```
- addedInput schema / properties / includePaths / maxItems
```
Added value: +20
```
- addedInput schema / properties / includeSubdomains / description
```
Added value: +"Treat subdomains of the same site as part of it."
```
- addedInput schema / properties / limit / default
```
Added value: +1000
```
- changedInput schema / properties / limit / description
```
Previous value: -"Urls to return (default 1000, max 5000)."New value: +"Urls to return. Up to 5000."
```
- addedInput schema / properties / limit / maximum
```
Added value: +5000
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / search / maxLength
```
Added value: +200
```
- addedInput schema / properties / search / minLength
```
Added value: +1
```
- changedInput schema / properties / url / description
```
Previous value: -"The site to map."New value: +"Page to process."
```
- addedInput schema / properties / url / format
```
Added value: +"uri"
```
First observedSep 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds the credit and dollar cost model, the browser-vs-no-browser distinction for includePage, and an API reference link. It stops short of describing the return shape or rate limits.

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?

Dense and front-loaded: capability first, then the decision heuristic, then cost, then the reference link. Every sentence carries information, though the cost figures appear twice (credit and dollar) without added nuance.

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 7-param read-only tool with full schema coverage and rich annotations, the description supplies the missing decision context and cost model. With no output schema, it partially compensates by saying what is returned (sitemap urls plus page links), though pagination and response format are not addressed.

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 all seven parameters are already documented, including the includePage cost tradeoff and the excludePaths-wins-over-includePaths precedence. The description only adds cost framing that the schema largely duplicates, so the baseline 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?

States a specific verb and resource ('every url of a site') plus the exact mechanism (sitemap plus optional page links). It is clearly distinguishable from web_crawl and web_scrape siblings without opening a 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?

Explicitly tells the agent to use it 'BEFORE crawling, to see what is there and decide what is worth reading', which gives context and sequencing. It refers to crawling as a concept rather than naming the web_crawl sibling, so it falls just short of the explicit-alternative bar.

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

All oassis — web scraping, crawling and browser control for AI agents tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?