Skip to main content
Glama
Sign In

Brent Burgess

by com.brentburgess
OverviewDiscussionsAdmin

Read a post, case study or page

fetch
Read-onlyIdempotent

The full text of a post, case study, page or project as Markdown, or one section of it. The id can be an id from search or list_content (such as "work/sleep-anchor"), a path ("/about"), a brentburgess.com URL, a brentburgess:// URI or a unique slug ("consulting"). Add #anchor for one section, as search results do.

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
idYesWhat to read: an id, path, URL, URI or slug, with an optional #anchor

Output Schema

NameRequiredDescriptionDefault
idYesIts id, with #anchor when one section was read
urlYesIts URL, with #anchor when one section was read
textYesThe text as Markdown, links absolute
titleYesIts title
metadataYesAbout the text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / metadata / properties / brief / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "built": {
-        "description": "What was built, in one sentence",
-        "maxLength": 200,
-        "type": "string"
-      },
-      "changed": {
-        "description": "What changed, in one sentence",
-        "maxLength": 200,
-        "type": "string"
-      },
-      "problem": {
-        "description": "The problem, in one sentence",
-        "maxLength": 200,
-        "type": "string"
-      }
-    },
-    "required": [
-      "problem",
-      "built",
-      "changed"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "built": {
+        "description": "What was built, in one sentence",
+        "maxLength": 200,
+        "type": "string"
+      },
+      "changed": {
+        "description": "What changed, in one sentence",
+        "maxLength": 200,
+        "type": "string"
+      },
+      "problem": {
+        "description": "The problem, in one sentence",
+        "maxLength": 200,
+        "type": "string"
+      },
+      "role": {
+        "description": "What Brent did, and what AI or others did, in one sentence",
+        "maxLength": 200,
+        "type": "string"
+      }
+    },
+    "required": [
+      "problem",
+      "built",
+      "role",
+      "changed"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / metadata / properties / brief / description
      Previous value: -"A case study’s summary in three sentences; null for a post or page"New value: +"A case study’s summary in four sentences; null for a post or page"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds useful behavior beyond that: the result is full text as Markdown, and #anchor selects one section. It does not mention error behavior when an id is missing or content size limits.

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 three tightly written sentences: the first front-loads the return type and resources, the second explains accepted id forms with examples, and the third explains section addressing. Every sentence earns its place with no filler.

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 single required parameter, full schema coverage, rich annotations and the presence of an output schema, the description supplies everything critical: what is returned, how ids are formed, and how to request a single section. No essential invocation context is missing.

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 description coverage is 100% and the schema already says id can be an id, path, URL, URI or slug with an optional #anchor. The description goes further by giving concrete examples of each format and explaining that #anchor retrieves one section, which is meaningful added semantics for the single parameter.

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?

It states a specific verb (read/fetch) and resource (post, case study, page or project) and names the return format (Markdown), which an agent can immediately distinguish from listing/search siblings. It also references ids from search and list_content, making its role in the toolset explicit.

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 implies the intended workflow: use ids from search or list_content, and add #anchor to retrieve a single section. It does not explicitly state when not to use this tool, but the reference to search/list_content as id sources gives clear usage context.

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

All Brent Burgess 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