Skip to main content
Glama
onthecheap-mcp

onthecheap-mcp

by chrischall

Get an On the Cheap article

otc_get_post
Read-onlyIdempotent

Fetch a full On the Cheap article by id, slug, or URL for a required city site, returning readable text or optional markdown/html formats.

Instructions

Fetch one "on the Cheap" article in full by numeric id, slug, or full URL. Pass the site key for the city the article belongs to — an id or slug from one site will not resolve on another, and a full URL must match the site you name. Returns the article text as readable plain text by default; set format to "markdown" to keep its links, headings and lists, or "html" for the original markup. Read-only.

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": {
      "site": "<site>",
      "post": "<post>"
    },
    "name": "otc_get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesPost id, slug, or full article URL
siteYesWhich "on the Cheap" city to read. Required — there is no default site. One of: charlotte, denver, atlanta, chicago, columbus, seattle, kansascity, miami, orlando, portland, richmond, southernmaine, triangle, national. Common aliases also work (milehigh, raleigh, rva, southflorida, kc, …). Use otc_list_sites for the full list with the area each one covers.
formatNoBody format: "text" (default, readable plain text), "markdown" (keeps links with their targets, headings, lists and emphasis) or "html" (the raw markup)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / format / description
      Previous value: -"Body format: readable text (default) or raw HTML"New value: +"Body format: \"text\" (default, readable plain text), \"markdown\" (keeps links with their targets, headings, lists and emphasis) or \"html\" (the raw markup)"
    • changedInput schema / properties / format / enum
      Previous value: -[
      -  "text",
      -  "html"
      -]New value: +[
      +  "text",
      +  "markdown",
      +  "html"
      +]
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the "Read-only" phrase is redundant. What the description adds beyond them is substantive: the cross-site resolution failure mode (an id or slug from one site will not resolve on another, and a URL must match the named site) plus the default plain-text rendering behavior.

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?

Three front-loaded sentences, scoped first by what is fetched and then by the site constraint and output format — good ordering with no padding. The trailing one-word "Read-only" sentence duplicates the annotation and is the only content that does not earn its place.

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 no output schema, the description carries the return-value burden and does so by explaining the three body renderings and the default. It stops short of describing any accompanying metadata (title, date, author) an agent might need to expect, which keeps it from a 5.

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. The description goes further by stating a cross-parameter constraint the schema does not encode: `post` and `site` must be consistent, and a full URL has to belong to the site named. It also summarizes the three `format` modes, though that repeats the enum descriptions.

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?

States a specific verb and resource — "Fetch one 'on the Cheap' article in full" — and pins the acceptable identifiers (numeric id, slug, full URL). The emphasis on a single full article implicitly separates it from search/list siblings such as otc_search_posts without needing to name them.

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?

Clearly establishes the use case (retrieve one known article) and adds a real precondition: the `site` argument must match the article's city. It does not explicitly say when to prefer otc_search_posts instead, but the single-article scope makes the boundary reasonably inferable.

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