Skip to main content
Glama

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

Diaspora opportunities and deadlines

get_diaspora_opportunities
Read-only

Diaspora opportunities and deadlines. Open grants, RFPs, fellowships and programs relevant to diaspora businesses, each verified at its primary source before listing, with deadlines. Filter by country, topic tag, or deadlines closing within N days. $0.1 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_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNotopic tag, e.g. grants, rfp (optional)
countryNocountry tag on the item, e.g. US, KE (optional)
closing_within_daysNoonly items with a deadline within this many days (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses provenance ('each verified at its primary source before listing'), the price ($0.1 USDC on Base), and the exact x402 handshake (402 → PAYMENT-SIGNATURE → delivery). It also resolves the critical ambiguity that calling this tool is free and payment only occurs at the returned URL, which an agent could not infer from annotations or schema.

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?

The content is front-loaded with what the tool returns, then filters, then the payment mechanics in the order an agent needs them. The opening 'Diaspora opportunities and deadlines' largely restates the title, and the payment sentence is dense, but no sentence is wasted.

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 no output schema, the description carries the return-value burden and does explain that it returns an x402 URL to GET plus the payment sequence. It does not describe the shape of individual opportunity records (fields, deadline format), a minor remaining gap for a listing tool.

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 all three optional parameters are already documented in the schema. The description restates their purpose (country, topic tag, closing within N days) but adds no format or edge-case detail, so the schema continues to do the heavy lifting; baseline 3 applies.

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?

The description names a specific resource and scope: 'Open grants, RFPs, fellowships and programs relevant to diaspora businesses,' plus verification at primary source and deadline coverage. That is far more specific than the bare title, and the content type is clearly distinct from siblings like get_diaspora_events or get_diaspora_jobs_snapshot, though no sibling is named 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?

It states the usable filter contexts (country, topic tag, deadlines within N days) and that all parameters are optional, which tells an agent how to shape a call. It stops short of explicit when-not-to-use guidance or naming an alternative for overlapping needs such as events or business listings.

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