Skip to main content
Glama

Primer Market Systems (MSD) & DCED Engine

search_opportunities

Read-onlyIdempotent

Search active, future-closing Market Systems Development (MSD), value chain, financial inclusion, and social enterprise RFPs, EOIs, grants, and consultancies aggregated from UNGM, UNDP, ReliefWeb, EU TED, and FinDev Gateway.

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": "search_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order for returned solicitations.deadline_asc
donorNoFilter by issuing agency or organization (e.g., UNDP, UNOPS, FAO, ITC, UNIDO, SNV).
limitNoMaximum number of active opportunities to return (1-25).
queryNoOptional keywords (e.g., climate microfinance, incubator, Cambodia, MSME, FAO).
regionNoFilter by exact geographic region.
categoryNoFilter by Market Systems or Social Enterprise practice category.
modalityNoDeprecated alias for contract_type.
eligibilityNoFilter by vendor eligibility (International Open vs Local Vendors Only).
contract_typeNoFilter by contract type or solicitation format (preferred alias for modality).
max_days_leftNoMaximum days remaining until closing deadline (1-365).

Output Schema

NameRequiredDescriptionDefault
countNo
totalNo
updated_atNo
opportunitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / contract_type
      Added value: +{
      +  "description": "Filter by contract type or solicitation format (preferred alias for modality).",
      +  "enum": [
      +    "Firm / Institutional RFP",
      +    "Individual Consultancy",
      +    "Consultancy (Firm or Individual)",
      +    "Call for Proposals / Grant"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / modality / description
      Previous value: -"Filter by contract type or solicitation format."New value: +"Deprecated alias for contract_type."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety and purity are covered. The description adds genuine context by naming the upstream aggregators (UNGM, UNDP, ReliefWeb, EU TED, FinDev Gateway), which tells the agent about coverage and freshness. It says nothing about pagination behavior, result caps, or ranking, which would have raised the score.

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?

A single front-loaded sentence led by the verb, with no filler. The trailing source list is dense but each element earns its place by defining data coverage.

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?

An output schema exists, so return values need not be explained, and all ten optional parameters are documented in the schema. What remains missing is guidance on filter combinations and result-cap behavior for what is otherwise a fairly complex 10-parameter query 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 description coverage is 100% with six enums fully described, so the schema carries parameter meaning. The description adds no syntax, default, or interaction details beyond that, leaving it at the baseline for a fully documented schema.

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?

Uses a specific verb (Search) plus the resource (RFPs, EOIs, grants, consultancies) and adds two meaningful qualifiers: 'active, future-closing' and the five named source aggregators. That makes it clearly distinct from search_msd_knowledge and get_opportunity without naming them, so it falls just short of a 5.

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 phrase 'active, future-closing' implies the search should be used for open funding calls, and the source list implies breadth-first discovery. But there is no explicit when-to-use or when-not guidance, no pointer to get_opportunity for full details on a single listing, and no advice about how the query parameter interacts with the structured filters.

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.