Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gdelt_tonechart

Generate a sentiment histogram for any GDELT query, showing tone distribution with article counts and sample titles/URLs. Filter by country, language, domain, or time window.

Instructions

Sentiment histogram for a GDELT query. Returns a sentiment histogram for the required GDELT query: one bin per integer tone value, each with an article count and a short sample of top articles with title and URL. Filter with country, language, domain, and timespan or from and to. A tone value with no matching articles is absent rather than returned with a zero count.

Input Schema

NameRequiredDescriptionDefault
toNoEnd of an absolute time window. Same formats as from.
fromNoStart of an absolute time window. Accepts YYYY-MM-DD, RFC3339, or GDELT's raw YYYYMMDDHHMMSS. Cannot be combined with timespan.
queryYesGDELT query string. Same syntax as gdelt-search's query.
domainNoConvenience domain filter, appended to the query as domain:VALUE.
countryNoConvenience source-country filter, appended to the query as sourcecountry:VALUE.
languageNoConvenience source-language filter, appended to the query as sourcelang:VALUE.
timespanNoRelative time window ending now, e.g. 1h, 2d, 1w, 3m. Cannot be combined with from/to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4/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 well: it discloses the return shape (one bin per integer tone value, each with count plus sample article title and URL) and a non-obvious edge behavior — tone values with no articles are omitted rather than returned as zero counts. It omits auth/rate-limit context, but the output and sparsity disclosures are meaningful beyond structured fields.

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-loaded with the core purpose and free of padding. The first sentence ('Sentiment histogram for a GDELT query') is largely restated by the opening of the second ('Returns a sentiment histogram for the required GDELT query'), a minor redundancy, but overall tight and well ordered.

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 describe the return payload — and it does, specifying bins, per-bin counts, and sample article metadata, plus the zero-count omission rule. For a seven-parameter query tool this is complete enough to invoke correctly.

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 coverage is 100%, so the schema already documents all seven parameters, including the timespan-vs-from/to exclusivity. The description only restates the filter names without adding syntax, formats, or semantics beyond what the schema provides — the baseline 3 for high coverage.

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 ('Sentiment histogram for a GDELT query') and immediately elaborates that it returns one bin per integer tone value with counts and sample articles. This clearly separates it from gdelt_search (article retrieval) and gdelt_timeline (time series) without the agent needing to open the schema.

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 explains how to filter but never states when to choose this tool over the closely related gdelt_timeline or gdelt_search. Usage is only implied by the phrase 'Sentiment histogram,' leaving the agent to infer that tone distribution analysis is the target scenario.

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