Rafe Blandford — career and writing

Search the writing

search_writing

Read-onlyIdempotent

Keyword search over everything published on rafeblandford.com — the FULL TEXT of every post, plus the About and Career pages.

Deterministic by design: it matches titles, tags, excerpts and body text and ranks by a fixed score. No model, no embeddings — the same query always returns the same results.

Returns metadata and an excerpt, not the body. Call get_post with a result's slug for the full text.

A blank query returns the most recent items. Combine it with topic to browse one section of the site.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results. Default 10.
`query`	No	Words or a phrase. Blank returns the most recent writing.
`topic`	No	Optional. Restrict to one of the site's topic groups: work, ai-work, product-tech, rafeos, all-about-archive, notes. Every response lists them in `available_topics` with counts.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`topic`	No
`corpus`	No
`results`	Yes
`total_matched`	Yes
`interpretation`	Yes
`available_topics`	No

TDQS

A4.7/5.0

Behavior5/5

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

The description goes beyond the readOnly and idempotent annotations by disclosing deterministic behavior ('No model, no embeddings — the same query always returns the same results') and the fixed-score ranking. It also states that only metadata and an excerpt are returned, not the body, which is a key behavioral trait.

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?

Three sentences, each carrying essential information: scope, determinism, and usage guidance. No filler or repetition.

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?

With an output schema present and readOnly annotations, the description covers the essential behavior, return format limitations, and usage patterns. It even provides guidance on using the tool for browsing via blank query and topic, making it complete for its complexity.

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?

The input schema already has 100% description coverage for all three parameters. The description adds a minor usage suggestion to combine query with topic for browsing, but does not provide substantial additional meaning beyond the schema.

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 uses the specific verb 'search' and the resource 'everything published on rafeblandford.com', including the full text of posts and About/Career pages. It clearly distinguishes itself from get_post by noting it returns metadata and an excerpt, not the body.

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

Usage Guidelines5/5

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

The description explicitly instructs users to call get_post with a result's slug for full text, providing a direct alternative. It also explains when blank queries and topic filtering are useful, giving clear context for when to use this tool.

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

All Rafe Blandford — career and writing tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool serves a distinct purpose: check_experience answers whether a topic is evidenced, get_evidence returns predefined sections, search_writing performs keyword search, and get_post retrieves full posts by slug. There is no meaningful overlap that would cause confusion.

Naming Consistency5/5

All tool names follow the verb_noun pattern (check, get, get, search). The style is consistent and intuitive, with no mixing of conventions or vague verbs.

Tool Count5/5

Four tools is well-scoped for a personal career and writing site. Each tool is necessary and has a clear role, covering both structured queries (evidence, sections) and content retrieval (search, fetch).

Completeness4/5

The tool surface covers the core workflows: checking experience, retrieving profile/career/case studies, searching writing, and fetching full posts. A minor gap is the lack of a way to enumerate all posts or browse the full archive beyond the most recent items returned by a blank search.

Resources

Need Help?