Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bloomberg_headlines

Fetch current Bloomberg story cards for a chosen editorial section by slug, returning each item’s title, canonical URL, and optional description, image, and publication time.

Instructions

Get the latest stories in a Bloomberg section. Returns current Bloomberg story cards for one editorial section. section is required and takes a slug from the Bloomberg categories list, such as markets, economics or politics. Each item has a title and canonical URL, and may also carry a description, image and publication time.

Input Schema

NameRequiredDescriptionDefault
sectionYesSection slug from /bloomberg/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It explains the return shape (title, canonical URL, optional description/image/publication time), which is useful, but says nothing about auth needs, rate limits, or ordering/count of returned items.

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 core action, then details input requirements and return shape. Four tight sentences with no filler, though slightly more could be trimmed without loss.

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-param read tool with no output schema, the description covers input sourcing and return fields. Minor gaps remain around result ordering and volume, but overall it is complete enough for correct invocation.

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?

Schema coverage is 100% so the schema documents 'section' already, but the description adds real value: it explains section is a slug drawn from the categories list and gives concrete examples. This goes beyond the bare schema description.

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+resource ('Get the latest stories in a Bloomberg section') and clarifies scope as one editorial section. It distinguishes itself from a general news listing by framing around a single section, though it doesn't explicitly name the sibling bloomberg_news.

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?

Clearly indicates the required input and steers the agent to the categories list for valid slugs, with example values (markets, economics, politics). It lacks explicit when-to-use-vs-alternatives routing (e.g. vs bloomberg_news), but the usage context is clear.

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