Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

investopedia_headlines

Retrieve current Investopedia headlines from any section. Provide a section slug to get article titles, URLs, bylines, and images in clean JSON.

Instructions

Get Investopedia section headlines. Returns the current story list from one Investopedia section, with title, URL, byline, and image. section accepts any slug returned by GET /investopedia/sections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesInvestopedia section slug, from GET /investopedia/sections

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?

With no annotations provided, the description carries the behavioral burden. It discloses the read-only nature ('Get', 'Returns'), the dynamic 'current story list', and the returned fields. It does not mention pagination, ordering, error behavior, or rate limits, but for a simple read operation this is minimally adequate.

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?

The description is two sentences, front-loaded with the verb and resource, and every sentence adds useful information. There is no filler or repetition beyond the schema reference, which is brief and relevant.

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?

For a one-parameter read-only tool with no output schema, the description is complete: it specifies the parameter source, the returned item fields, and the scope. Nothing an agent needs in order to invoke it correctly is missing.

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 single section parameter is fully described and enumerated in the schema. The description's mention that section accepts any slug from GET /investopedia/sections largely restates the schema, adding little new semantic value beyond what the schema already provides.

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 clearly states the verb ('Get'), the resource ('Investopedia section headlines'), and the output fields (title, URL, byline, image). It is scoped to a single section, which helps distinguish it from section-list or article-level sibling tools, though it does not explicitly name any sibling.

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?

The description implies usage context by saying it returns the current story list from one Investopedia section and that section accepts slugs from GET /investopedia/sections. However, it does not explicitly state when to prefer this over related tools like investopedia_news or investopedia_sections, nor does it provide exclusions.

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