Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thisismoney_headlines

Fetch current This Is Money headlines for one section, returning titles, URLs, summaries, authors, publication times, and images.

Instructions

Get This Is Money section headlines. Returns the current headlines for one This Is Money section. section is required and takes one of money, markets, investing, savings, pensions, mortgages, property, cars, travel or consumer. Each item has its title and URL, plus summary, author, publication time and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesThis Is Money section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return shape (title, URL, summary, author, publication time, image 'when the outlet provides them'), but says nothing about rate limits, result count/caps, caching, or freshness beyond 'current'.

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?

Front-loads the purpose, then the required parameter, then the return fields, in three efficient sentences. The only waste is re-enumerating the enum values already present in the schema.

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 single-parameter read tool with no annotations and no output schema, the description covers what it does, the mandatory input, and the shape of returned items. No critical gap remains for correct invocation.

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 coverage is 100% and the enum already documents all valid `section` values, so the description's re-listing of them adds no new semantic meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

The description uses a clear verb+resource ('Get This Is Money section headlines') and scopes it to a single section, which an agent can distinguish from the sibling thisismoney_sections (section list) and thisismoney_article (full content). It never explicitly names those siblings, so differentiation is inferred rather than stated.

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 states that `section` is required and enumerates valid values, which implies the calling context, but offers no explicit when-to-use or when-not-to-use guidance and names no alternative tool. Usage is left to inference from the siblings.

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