Skip to main content
Glama

Primer Market Systems (MSD) & DCED Engine

search_msd_knowledge

Read-onlyIdempotent

Search Primer International's global Market Systems Development (MSD / M4P) and Social Enterprise database (2,523 records across DCED, BEAM Exchange, MSD4E, SEWF, ILO The Lab, ANDE, WEF Schwab Foundation, and UN ESCAP).

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": {
      "query": "<query>"
    },
    "name": "search_msd_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of evidence matches to return (1-20).
queryYesSearch keywords or concepts (e.g., cost-share agreement, thin market mechanics, social procurement, work integration).
doc_typeNoFilter by evidence type.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered without description help. The description adds useful scope context (2,523 records, named contributing databases), which tells the agent the breadth of the corpus. It says nothing about ranking, matching behavior, or what a result record contains.

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?

A single front-loaded sentence with no wasted framing; the tool's identity and scope come first. The long parenthetical of source acronyms is dense but does communicate genuine corpus coverage rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only place that could describe result shape or ranking, and it does not. For a search tool with full schema coverage and complete annotations, most call-critical information exists, but the agent is left guessing about what evidence matches look like.

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% and every parameter carries its own explanation, including an enum for doc_type and a range note for limit. The description adds no syntax, format, or query-composition guidance beyond what the schema already provides, so the 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?

States a clear verb ('Search') plus a named resource ('Primer International's global MSD/M4P and Social Enterprise database') and quantifies the corpus size with named source collections. An agent can immediately tell this retrieves knowledge-base evidence rather than opportunities or calculations like the siblings. It stops short of explicitly differentiating itself from search_opportunities, which is the nearest potential overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description contains no when-to-use, when-not-to-use, or alternative-routing guidance. It never tells the agent whether this is the right tool for evidence lookup versus the sibling search_opportunities or lint_proposal. The only usage signal is implicit in the word 'Search'.

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.