Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bloomberg_article

Fetch a public Bloomberg article by URL and return its title, authors, timestamps, section, categories, image, premium status, and ordered body paragraphs.

Instructions

Get a Bloomberg article's content. Returns a public Bloomberg article by url: title, description, publication and update times, section, categories, authors, image, is_premium and the body paragraphs in order. Subscriber-only articles that Bloomberg shows as a truncated preview return 403, an article with no body returns 503, and non-article or non-Bloomberg URLs return 400.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Bloomberg article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the return shape (paragraphs, is_premium, authors) and the concrete failure modes (403 for subscriber-only truncated previews, 503 for no body, 400 for non-article or non-Bloomberg URLs). Missing only rate-limit or auth notes.

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?

Three tight sentences, purpose front-loaded, followed by return fields and then error semantics. No filler; every sentence carries information an agent needs.

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?

No output schema exists, so the description must explain returns, and it enumerates them comprehensively. Combined with the error-code handling for a single required URL parameter, nothing an agent needs to call this 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 url param already documents itself as a 'Canonical Bloomberg article URL.' The description adds no syntax, format, or resolution detail beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb and resource ('Get a Bloomberg article's content') and scopes it precisely to a 'public Bloomberg article by url.' The field list (title, paragraphs, is_premium) makes clear this is the article-detail fetch, distinct from siblings like bloomberg_news and bloomberg_headlines.

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 implied by the required url parameter and the 'public article' framing, but the description never says when to reach for this tool versus alternatives (e.g., use bloomberg_news or bloomberg_headlines first to discover a URL). No explicit exclusions or prerequisite guidance.

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