Skip to main content
Glama

Tako

by io.github.TakoData
OverviewDiscussionsAdmin

Tako: Fetch Contents

tako_contents
Read-onlyIdempotent

Fetch the full content behind a url: a web page's text, or an exportable Tako card's data rows. Batch up to 10 urls in one call — each fails on its own.

Fetch only cards that tako_search marked exportable: true. Set max_rows when the recent rows are enough. If a page is long, such as a filing or an annual report, set query to a question to get back only the passages that answer it.

Best for: reading one source in full — a page you need to quote, or the rows behind a card you need to compute over.

Input Schema

NameRequiredDescriptionDefault
urlsYesThe urls to fetch: a Tako card url or a web result url. One call for 8 urls saves 7 round trips.
queryNoWeb pages only: a question the passages should answer. The result holds those passages instead of the page. Omit it to get the whole page.
formatNoTako cards only. `rows` returns the card's data as one table. `card` returns the card's own structure, such as a company card's tabs or a game's box score. A card type without its own structure returns `rows`. Web pages ignore it.
deliveryNoTako cards only. `inline` returns the data in the result. `link` returns a download link: a CSV file, or a JSON file with `format: "card"`. It expires in 5 minutes. Use `link` when you can run shell commands and want to analyze the data in code. If the download fails, call again inline with `max_rows` at 2,000 or less.
max_rowsNoTako cards only: how many rows to return. Omit it to get up to 2,000 rows. With `delivery: "link"`, you can raise it to 100,000. Charges scale with rows returned, so lower it when the recent rows are enough.
max_charsNoWeb pages only: character cap on the extracted text. Inline fetches default to 100,000 per url, less across a batch. Raise it for a long document; `truncated` reports a cut. With `query`, it caps the passages instead: 100 to 20,000, and 4,000 by default.

Output Schema

NameRequiredDescriptionDefault
usageYesWhat this request cost.
resultsYesOne per requested url, in order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / delivery
      Added value: +{
+  "description": "Tako cards only. `inline` returns the data in the result. `link` returns a download link: a CSV file, or a JSON file with `format: \"card\"`. It expires in 5 minutes. Use `link` when you can run shell commands and want to analyze the data in code. If the download fails, call again inline with `max_rows` at 2,000 or less.",
+  "enum": [
+    "inline",
+    "link"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Tako cards only. `rows` returns the card's data as one table. `card` returns the card's own structure, such as a company card's tabs or a game's box score. A card type without its own structure returns `rows`. Web pages ignore it.",
+  "enum": [
+    "rows",
+    "card"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / max_rows / description
      Previous value: -"Tako cards only: how many rows to return. Omit it for the whole card, up to 2,000 rows. Every row delivered is billed, so lower it when the recent rows are enough."New value: +"Tako cards only: how many rows to return. Omit it to get up to 2,000 rows. With `delivery: \"link\"`, you can raise it to 100,000. Charges scale with rows returned, so lower it when the recent rows are enough."
    • changedInput schema / properties / max_rows / maximum
      Previous value: -2000New value: +100000
    • changedInput schema / properties / urls / description
      Previous value: -"The urls to fetch: a Tako card url or a web result url. One call for 8 urls costs the same as 8 separate calls and saves 7 round trips."New value: +"The urls to fetch: a Tako card url or a web result url. One call for 8 urls saves 7 round trips."
    • addedOutput schema / properties / results / items / properties / card
      Added value: +{
+  "additionalProperties": {},
+  "description": "The card's structure.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / results / items / properties / download
      Added value: +{
+  "additionalProperties": false,
+  "description": "The file, in link mode.",
+  "properties": {
+    "expires_at": {
+      "type": "string"
+    },
+    "file_format": {
+      "enum": [
+        "csv",
+        "json"
+      ],
+      "type": "string"
+    },
+    "total_rows": {
+      "description": "Rows behind the card, before `max_rows`.",
+      "type": "number"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "expires_at",
+    "file_format"
+  ],
+  "type": "object"
+}
    • changedOutput schema / properties / results / items / properties / error / description
      Previous value: -"Why this url alone failed; the others are unaffected."New value: +"Why this url failed."
    • changedOutput schema / properties / results / items / properties / note / description
      Previous value: -"Whether `text` holds the passages for `query` or the whole page."New value: +"Whether `text` is passages or the whole page, or a card fell back to rows."
    • changedOutput schema / properties / results / items / properties / text / description
      Previous value: -"Web pages only: the page text, or its passages when `query` is set."New value: +"Web pages only: the page text or its passages."
  2. Changed4 schema fields changed
    • changedInput schema / properties / max_chars / description
      Previous value: -"Web pages only: character cap on the extracted text. Inline fetches default to 100,000 per url, less across a batch. Raise it for a long document; `truncated` reports a cut."New value: +"Web pages only: character cap on the extracted text. Inline fetches default to 100,000 per url, less across a batch. Raise it for a long document; `truncated` reports a cut. With `query`, it caps the passages instead: 100 to 20,000, and 4,000 by default."
    • changedInput schema / properties / query / description
      Previous value: -"Web pages only: return the passages around matches of this phrase instead of the whole page. The full page is always scanned, so no match means the phrase isn't there."New value: +"Web pages only: a question the passages should answer. The result holds those passages instead of the page. Omit it to get the whole page."
    • changedOutput schema / properties / results / items / properties / note / description
      Previous value: -"What the `query` match found."New value: +"Whether `text` holds the passages for `query` or the whole page."
    • changedOutput schema / properties / results / items / properties / text / description
      Previous value: -"Web pages only: the page text."New value: +"Web pages only: the page text, or its passages when `query` is set."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations, the description discloses batching behavior, per-URL failure isolation, exportability constraints, charge scaling with rows, link expiry, and fallback behavior if a download fails. This is substantial operational context not present in the annotations.

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?

The description is front-loaded with the core action and then organized into practical constraints and use guidance. Every sentence contributes either scope, routing, or operational behavior, with little waste.

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

Completeness5/5

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

Given the output schema and annotations, the description covers the remaining gaps an agent needs: what can be fetched, batching limits, failure isolation, exportable cards, long-document querying, row limits, and delivery tradeoffs. It is complete for correct invocation.

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?

The schema already documents all six parameters at 100% coverage, so the baseline would be 3. The description adds useful decision guidance for batching, max_rows, and query use on long pages, though it does not add much beyond the schema for format, delivery, or max_chars beyond what is already structured.

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: fetching full content behind URLs, including web page text and Tako card rows. It clearly distinguishes content retrieval from sibling search by emphasizing full-source reading and the exportable-card constraint.

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?

It gives explicit usage direction: use this to read one source in full, fetch only cards marked exportable by tako_search, batch URLs, and use query for long documents. It does not directly compare against tako_available_data or tako_graph_related, but the main routing guidance versus search is clear.

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

All Tako toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold 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