Skip to main content
Glama
seeker

seeker

by bottercode

get_contents

Retrieves a page's full text by URL, using the local index when available or fetching it live if not. Optionally limits returned characters with max_characters.

Instructions

Get the full text of a page: from the index if present, otherwise fetched live.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
max_charactersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations, so the description carries the full behavioral burden. It does disclose the index-first, live-fallback retrieval path, which is useful, but says nothing about what happens on fetch failure, paywalls, empty pages, or that results are truncated to max_characters.

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 well-formed sentence with the key mechanic (index, else live) front-loaded and no filler. Nothing extraneous to cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with zero annotation coverage, 0% schema coverage, and no output schema, the description is far too thin. It never explains return shape, truncation via max_characters, or failure modes, so an agent cannot call it confidently beyond the happy path.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain both parameters and does not. The url parameter is implied but max_characters is never mentioned, leaving the caller unaware that output is truncated at 8000 characters by default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get the full text of a page") plus a meaningful scope detail about the index-vs-live source. It is distinguishable from web_search and find_similar by being a direct URL content fetch, though it never names or contrasts those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: call it with a URL when you need the page's full text. There is no explicit when-to-use vs when-not guidance, no mention of preferring it over web_search for known URLs, and no note on cost/latency differences between an index hit and a live fetch.

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