Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

sfgate_headlines

Fetch current SFGate headlines for a chosen section, such as top-news, bay-area, sports, or food-dining, and return 12–30 stories as clean JSON.

Instructions

Get SFGate section headlines. Returns the latest SFGATE stories for one section. section is required and takes top-news, bay-area, business-technology, entertainment, celebrity, food-dining, travel, routes, top-sports, giants, 49ers or warriors. Feeds hold 12 to 30 items, and the warriors feed is quiet in the off-season.

Input Schema

NameRequiredDescriptionDefault
sectionYesSFGate section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add genuine behavioral context beyond the schema: feed depth (12 to 30 items) and a notable staleness quirk ('the warriors feed is quiet in the off-season'). It still doesn't state freshness/ordering guarantees or whether the call is unauthenticated, but the two operational hints it gives are exactly the kind of detail an agent cannot infer.

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 sentences with purpose first, then parameter, then caveats, and no filler. The prose enumeration of all twelve slugs is mildly redundant against the schema enum, which keeps it just short of a 5.

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?

For a one-parameter, no-output-schema read tool, the description covers what is fetched, the allowed inputs, typical result volume, and a known edge case. Only the shape of an individual returned item is left unstated, which is a minor gap.

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 100% and the section property already carries a complete enum, so the baseline is 3. Restating the allowed slugs in prose adds no semantics beyond the enum; the genuinely additive information (feed size, off-season quiet) concerns behavior rather than the parameter itself.

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: 'Get SFGate section headlines' and 'Returns the latest SFGATE stories for one section.' That is unambiguous for an agent. It does not, however, distinguish itself from the close siblings sfgate_news or sfgate_sections, so the agent must guess which SFGate retrieval tool to pick.

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

Usage Guidelines3/5

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

It establishes that section is required and enumerates the valid values, which implies the intended usage, but never says when to use this over sfgate_news or sfgate_sections, nor what it does not cover (e.g., article bodies). Usage is inferable but not stated.

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

Deploy Server

Other Tools