Skip to main content
Glama
Sign In

Littles Weekly

by com.littlesweekly
OverviewDiscussionsAdmin

Get a page

get_page
Read-onlyIdempotent

Everything on one Littles Weekly page, in reading order: each section (Top 5 picks, Saturday and Sunday plans, every outing, Around town favorites, free days with who gets in free, always-free places, storytimes, indoor play with ages, prices, toddler times and sock rules, weekly library storytimes by day and branch, ice rinks with season dates, prices, skate rental and skate aids, Santa and lights listings, Christmas parades and tree lightings, Christmas train rides, what’s open on Dec 24, Dec 25 and Jan 1, getaway trips, tips), every card’s official link and "Checked" date, and the page FAQ. page is a key from list_pages, like "this-week", "guide", "visiting", "free", "indoor-play", "storytime", "ice-skating", "santa", "christmas-lights", "thanksgiving", "christmas-parades", "christmas-trains", "nutcracker", "christmas-markets", "christmas-break", "noon-years-eve" or "weekend-getaways". Long pages come back in parts: pass section to get one heading. format "markdown" returns the page’s Markdown version instead.

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": {
      "city": "<city>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYes
pageNoPage key from list_pages. Defaults to "this-week".this-week
formatNostructured (default) or markdown
sectionNoOnly the section whose heading contains this text, e.g. "Top 5", "Sunday", "always free", "FAQ".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real behavior beyond that, notably that long pages are returned in parts and that section isolates one heading, plus the markdown alternative return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a sprawling parenthetical catalogue of every section ('Santa and lights listings... toddler times and sock rules') that advertises content rather than helping the agent invoke the tool. The actionable facts—page keys, section filtering, markdown format—are buried behind it.

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?

Given no output schema, the description covers what comes back (sections in reading order, official links with Checked dates, FAQ), pagination, and format choices. Minor gap: it doesn't explain the special city value 'site', which only appears in the schema enum.

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?

Schema description coverage is 75% and already documents city slugs, page keys, format, and section semantics; the description largely restates these. The one added nuance is the pagination rationale for section, which the schema doesn't convey.

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 ('Everything on one Littles Weekly page, in reading order') and enumerates the content returned, so an agent knows it retrieves a whole page composition rather than events or search hits. It doesn't draw an explicit contrast with get_events or search, but naming page keys from list_pages implies the boundary.

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?

Explains that page must be a key from list_pages with concrete examples, and tells the agent to pass section to get a single heading when pages are long. There is clear context for the format switch to markdown, but no explicit 'when not to use this' versus search or get_events.

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

All Littles Weekly 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