Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thisismoney_news

Fetch current This Is Money top stories as structured JSON with titles, URLs, summaries, authors, publication times, and images; no parameters required.

Instructions

Get This Is Money top stories. Returns the current top stories from This Is Money. It takes no parameters. Each item has its title, URL and, where available, a summary, author, publication time, image URL and type. Use the headlines endpoint to read one section.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the return fields (title, URL, summary, author, publication time, image URL, type), which is genuinely useful since there is no output schema, but it says nothing about result count, pagination, freshness, or whether the call can fail.

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

Conciseness3/5

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

Sized reasonably and front-loaded, but the first two sentences say the same thing ('Get This Is Money top stories' / 'Returns the current top stories from This Is Money'), so one sentence does not earn its place.

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 parameters and no output schema, the description should explain the return shape, and it does list the item fields, including that summary and image are conditional. Only secondary details (item count, ordering, update cadence) are missing, which is minor for a read-only feed.

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?

The tool takes zero parameters, which is the baseline-4 case. The sentence 'It takes no parameters' repeats what the empty schema already shows, adding no meaning, but nothing is left ambiguous.

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 This Is Money top stories') and clarifies the scope is the current top stories rather than a section, which separates it from thisismoney_headlines. It is clear, though the differentiation from siblings is implied rather than named by tool name.

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?

Explicitly routes the agent to an alternative: 'Use the headlines endpoint to read one section.' That tells the agent when to prefer a sibling, but it gives no exclusion for thisismoney_article or thisismoney_author, so guidance is clear but not complete.

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