Skip to main content
Glama
Sign In

BOZOS

by si.bozos
OverviewDiscussionsAdmin

Read a BOZOS resource

fetch
Read-onlyIdempotent

Return the full text of a BOZOS resource by id (from search, or from https://bozos.si/content-index.json): the Markdown version of a guide or note, or a JSON dataset. Pass agent-recipes#check-existing-text for one executable recipe, a record permalink (https://bozos.si/ai-crawlers.json#gptbot) or # to get one record. Cite the returned url.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesResource id (ai-crawler-directory-data), or a record: ai-crawler-directory-data#gptbot or https://bozos.si/ai-crawlers.json#gptbot

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "metadata": {
+      "type": "object"
+    },
+    "text": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "title",
+    "url",
+    "text",
+    "metadata"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely behavioral detail beyond them: the two retrieval modes (whole resource vs single record) and the obligation to cite the returned url. It omits what happens on unknown ids or very large resources.

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?

Two sentences, front-loaded with the core action and payload types, then the id-form variants and the citation rule. Dense but every clause carries information; the parenthetical URL and example are load-bearing.

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 an output schema present, return values need no explanation, and annotations cover safety. The description covers id provenance, retrieval modes, and citation duty, leaving only edge-case behavior (missing id, size limits) undocumented.

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, but the description earns more by enumerating the accepted id forms — plain resource id, record permalink, and `<dataset id>#<record id>` — and tying each form to the returned shape, which the schema only partially conveys.

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: return the full text of a BOZOS resource by id, and clarifies that the payload is Markdown for guides/notes or JSON for datasets. It implicitly separates itself from `search` (which supplies the id) but never distinguishes itself from the sibling `readSource`, which is the most likely source of confusion.

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?

Gives concrete entry points for obtaining an id (`search`, the content-index.json URL) and states the conditions that produce a single-record response (record permalink or `<dataset id>#<record id>`). It lacks any explicit 'do not use this when…' guidance or comparison to `readSource`/`search`.

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

All BOZOS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources