Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

Diaspora opportunity event dates

get_diaspora_events
Read-only

Diaspora opportunity event dates. Dated events derived from the opportunities feed: announcement dates, application windows opening and deadlines, each tied to its parent item. Dates stated in the parent item only — not a general events calendar. $0.05 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_diaspora_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoannouncement_due, window_opens or deadline (optional)
afterNoonly events on or after this ISO date (optional)
beforeNoonly events on or before this ISO date (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare read-only/non-destructive/open-world; the description adds real operational context the agent otherwise wouldn't have: a $0.05 USDC cost on Base, a two-step x402 flow (402 → PAYMENT-SIGNATURE → delivery), and the crucial distinction that the tool call is free while the returned URL requires payment. It stops short of describing the delivered payload's shape or size, which matters for a paid endpoint.

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?

Short and front-loaded: purpose first, scope exclusion second, payment mechanics last. Nearly every sentence carries information, though the payment sentence is dense and packs pricing, protocol, and cost placement into one run-on.

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 three-optional-param read tool with no output schema, the description covers scope, cost, and the payment handshake adequately, and annotations handle safety. The main remaining gap is that an agent paying $0.05 is told nothing about what the delivered data looks like (fields per event, volume).

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% and each of the three optional params is documented in the schema, so the baseline applies. The description's enumeration of date types (announcements, windows opening, deadlines) loosely aligns with the `kind` values but adds no filtering semantics, date-format rules, or interaction between `after`/`before`.

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 the resource precisely ("Dated events derived from the opportunities feed: announcement dates, application windows opening and deadlines, each tied to its parent item") and scopes out a plausible confusion ("not a general events calendar"). It implicitly points at the parent feed (get_diaspora_opportunities) but never names it as the alternative, so differentiation is clear but not fully explicit.

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: reach for this when you need discrete dates rather than full opportunity records, and the "not a general events calendar" clause excludes one wrong mental model. There is no explicit statement of when to prefer this over get_diaspora_opportunities or when the parent feed is the better call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources