Skip to main content
Glama
AKzar1el

mcp-trendpulse

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_article_content

Read-only

Fetch and parse a specific news article by URL to retrieve its text, metadata, or a concise summary—ideal for analyzing or summarizing a known article without searching for new ones.

Instructions

Download and parse one specific news article when you already have an article URL. Use it to retrieve article text or metadata or summarize that URL; do not use it for discovery - use the news search tools instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the news article to download and parse.
full_dataNoReturn full data for the article. If False a summary should be created by setting the summarize flag
summarizeNoGenerate a summary of the article, will first try LLM Sampling but if unavailable will use nlp

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.13
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, and the description is consistent with those. It adds useful behavioral context beyond annotations by explaining that the tool retrieves article text or metadata and can summarize a given URL, clarifying what the operation actually performs.

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

Conciseness5/5

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

Two tight sentences with no filler. The core operation is front-loaded, and the exclusionary guidance is placed right after the primary use case.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description, combined with full schema coverage, a rich set of annotations, and an output schema, gives an agent everything needed to invoke the tool correctly. The only real decision point—discovery versus single-article retrieval—is addressed explicitly.

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%, so the schema already documents all parameters. The description adds context around the URL being a specific article URL rather than a discovery query, but it does not materially enrich the parameter semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: download and parse one specific news article using an article URL. It also explicitly contrasts itself with the discovery-focused sibling tools, making its scope unambiguous.

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

Usage Guidelines5/5

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

It clearly states when to use the tool (when you already have an article URL) and when not to use it ('do not use it for discovery - use the news search tools instead'). This gives an agent an explicit selection rule relative to the sibling tools.

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