Skip to main content
Glama
chrischall

charlotteonthecheap-mcp

by chrischall

Search a city’s On the Cheap articles

otc_search_posts
Read-onlyIdempotent

Find free and cheap things to do in a city by searching articles from the On the Cheap network. Filter by category, location, date, or full-text query, and optionally include expired deals.

Instructions

Search and filter one "on the Cheap" site's articles — free and cheap things to do in that city, plus deals, festivals, kids activities and local guides. Pass the site key for the city (see otc_list_sites); the national hub is valid here and carries country-wide deals. Filter by full-text query, category or location id (see otc_list_categories / otc_list_locations), and publication date range. Category and location ids are per-site — resolve them against the SAME site you are searching. Retired deals live in an "expired" category and are excluded by default; set include_expired to search them too. Returns slim summaries by default — use otc_get_post for an article's full text. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoTag id
pageNo1-based page number
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.
afterNoOnly posts published on or after this date
queryNoFull-text search, e.g. "free museum day"
beforeNoOnly posts published on or before this date
compactNoReturn slim summaries instead of full records (default true)
categoryNoCategory id from otc_list_categories, for this same site
locationNoLocation id from otc_list_locations, for this same site
per_pageNoResults per page (max 100)
include_expiredNoInclude retired/expired deals (default false)
Behavior5/5

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

Annotations already indicate readOnlyHint, idempotentHint, openWorldHint. The description adds context: read-only, default exclusions (retired deals), compact summaries, and date range filtering. No contradictions between description and annotations.

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?

The description is a single paragraph that packs essential information without excessive verbosity. Could benefit from light structuring (e.g., listing key points) but remains concise and front-loaded with core purpose.

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 11 parameters, no output schema, and no nested objects, the description covers site selection, filtering by query/category/location/date, expired deals, compact mode, and references to complementary tools. An agent has sufficient context to use the tool correctly.

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?

All 11 parameters have descriptions in the schema (100% coverage). The description adds value beyond the schema by explaining site aliases, per-site category/location resolution, query examples, and defaults (include_expired, compact).

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 clearly states the tool's purpose: 'Search and filter one on the Cheap site's articles' and specifies the content types (free/cheap things, deals, festivals, etc.). It differentiates from siblings like otc_get_post (full text) and otc_list_* (list metadata).

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?

The description provides guidance on when to use the tool (searching/filtering articles) and mentions alternatives (otc_get_post for full text). It explains the relationship with other tools (category/location ids per-site) and the national hub. Lacks explicit 'when not to use' but context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/charlotteonthecheap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server