Skip to main content
Glama
Sign In
Malja MCP

Malja MCP

Official
by marsaplatform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Situation reports

situation_reports
Read-only

Fetch yearly situation report counts and latest report titles and links for a country, with optional text filters, to ground trend and anomaly analysis in what was reported at the time.

Instructions

Situation reports published about a country: yearly counts plus the most recent report titles and links (ReliefWeb). Use it to ground trends and anomalies from other tools in what was actually reported at the time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "situation_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFree-text filter for the listed reports (e.g. "cholera") — yearly counts stay unfiltered
localeNoLanguage of the human-readable text output: "en" (default) or "ar" (Modern Standard Arabic, right-to-left). Structured JSON fields, ISO3 codes and dataset ids stay in English either way.
countryYesCountry name or ISO3 code, e.g. "Egypt", "EGY", "syria"
year_toNoLast year of the range (default: latest available)
year_fromNoFirst year of the range (default: 10 years back)
max_reportsNoHow many of the most recent reports to list (default 5)

Output Schema

NameRequiredDescriptionDefault
latestYes
sourceYes
countryYes
recordsYes
country_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.7.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and open-world nature are covered. The description adds real value with the ReliefWeb provenance and by clarifying the response mixes unfiltered aggregates with a short list of recent items, but it says nothing about result size, recency lag of the source, or rate limits.

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 sentences, zero filler, with the resource and payload front-loaded before the usage note. Every clause earns its place and nothing is repeated from the title.

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?

With an output schema, full parameter documentation and read-only annotations, the agent has everything needed to call it. The remaining gap is scope framing — how far back yearly counts extend and how current the listed reports are — which the description leaves to the defaults in the schema.

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%, including enums, defaults and bounds, so the baseline is 3. The description only implies the country parameter through 'about a country' and adds no semantics for query, locale, or the year range that the schema does not already spell out.

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 concrete verb and resource — situation reports published about a country — plus what they contain (yearly counts, recent titles and links) and the data source (ReliefWeb). It implicitly separates itself from profile/trend tools by positioning itself as the source-of-record layer, though it never names a sibling explicitly.

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?

Gives a clear positive use case: grounding trends and anomalies surfaced by other tools in what was actually reported at the time. It never states when not to use it or names a specific alternative (e.g. country_profile vs. trend_analysis), so the routing signal stops short of explicit.

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