Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thisismoney_article

Fetch This Is Money article content by canonical HTTPS URL to get title, authors, publication dates, image, body paragraphs, and paywall status for finance research.

Instructions

Get This Is Money article content. Returns one This Is Money article by url, a canonical HTTPS article link. The response has the title, description, section, authors, publication and update times, image URL, body paragraphs and a paywalled flag. Pages that are subscriber-only or blocked return an error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical This Is Money article URL

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 behavioral burden and does well: it enumerates the returned fields, exposes the `paywalled` flag, and warns that subscriber-only or blocked pages return an error rather than partial content. Missing only auth or rate-limit context, so it stops short of a 5.

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?

Two front-loaded sentences with the purpose stated first and the return shape and failure mode following. The inline field enumeration is a bit list-like but earns its place since no output schema exists.

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 and no annotations, the description must cover both purpose and return values, and it does so thoroughly, including the paywall flag and error case. Only the mechanics of obtaining a valid URL are left implicit, which is a minor gap for a single-parameter fetch tool.

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 there is only one parameter, so the schema already documents `url` as a canonical This Is Money article URL. The description's 'canonical HTTPS article link' phrasing restates rather than extends that, making the baseline 3 appropriate.

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 ('Get') and resource ('This Is Money article content') and clarifies it returns exactly one article keyed by url. The publisher-scoped name plus the singular 'one ... article' phrasing separates it from thisismoney_headlines and thisismoney_news, though the description never explicitly contrasts with those siblings.

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?

Usage is only implied: the required 'url' parameter signals this is a follow-up fetch after obtaining a canonical link, and the error note tells the agent some pages won't work. There is no explicit when-to-use/when-not or mention of which sibling to use for discovery.

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