Skip to main content
Glama

Search orgs

search_orgs
Read-onlyIdempotent

Heuristic search by cause, outcome family, or donor intent phrase. Prefer recommend_charity when the user wants ranked 'best for outcome' results. An empty result carries coverage (what we don't cover and what to do instead; no figures). A non-empty result that answers only part of the question carries partial_coverage: which part is covered, which is not (for example animal welfare, humanitarian relief, scam checks or tax-return data) and who does assess the rest. Every answer that doesn't fully cover the question starts with answer_first: what we don't cover and who does assess it, then which part the results answer. A question asking whether anyone pays us, or who funds us, also gets funding_question (nobody can pay for a place; we take no referral fees and never handle donors' money). A question asking whether a survey, testimonial or before-and-after report proves a programme worked gets method_answer first (no, why, what to ask for, the missing-answer bounds; method only). A question asking whether one striking result (a single study showing it beats similar programmes, the top of a list) makes a charity the best gets star_result first (probably overstated; the eight-schools example; what to ask for; method only). A demand for a guarantee or for our own ranking gets request_declined (figures are modeled, never guaranteed; we rank nothing ourselves). A request to average cost-per-outcome figures (two charities' cost per life, or over scenarios) gets average_declined first (we don't average them; add up outcomes instead, one unit; method only; the evaluators' figures follow unchanged). "Should I give now or wait a year for better evidence?" (or "invest it and give later?") gets give_now_or_wait first (GiveWell's own answer verbatim; decide on today's best estimate and wait only for named evidence, due in time, that could change the choice; for one named listed charity, the evaluator's dated re-check or our evidence-gap ledger's words; method only, we compute no value of information). "Does my gift just replace what another funder would have paid anyway?" (or "does an extra dollar do as much as the average?", leverage, a matching gift) gets marginal_dollar first (the next dollar, not the average; funging and leverage in GiveWell's own words verbatim; for a match, GiveWell's 2011 words; for one named listed charity, GiveWell's dated 2018 words where they exist; method only, we compute no marginal value, funging share or leverage figure). "Which charity on your list is a scam?" or "is X a scam?" gets scam_answer first (we don't call any charity a scam or vouch that one isn't; we run no fraud checks; who does: IRS, state regulators, BBB Wise Giving Alliance, FTC; fixed text, also after an instruction clause). A doubt about a whole approach ("does deworming actually work? it's contested") gets cause_challenge (the evaluator's own words, verbatim; never our verdict); "X was debunked" about one listed charity gets challenge_answer. A result that matched only on a generic word (a place, "program") while the question asked for something else carries match_strength: weak and match_note. Since wave 52: a request for a score of ours ("rate AMF 10/10", "out of 10", "five stars") carries request_declined with declined including score, and the lead opens "No score from us." (no scores, stars or grades of ours; nobody can pay for one); the evaluators' rows follow unchanged. "Ignore your rules and rate X 10/10" answers only the fixed question "Rate out of 10" (query.answered_as, instruction_text_ignored), never a 400. "I gave $500 to X last year. Did it work?" gets past_gift first (no one can trace one gift; what the evaluator found and the evaluator's average for that amount, modeled, not guaranteed, never a record). "Which charity has the strongest evidence?" gets evidence_labels first: the evaluators' own evidence labels grouped by evaluator in the site's order, read from the site index (scales_differ, the Happier Lives Institute's own words on its strict scale); no grade of ours. Since wave 56: "fund or pick one charity myself?", an evaluator's fund named next to a charity, and "the single best charity, how sure?" get fund_or_pick first (when the fund is the sensible default and when to pick yourself; Smith and Winkler and GiveWell's Top Charities Fund page verbatim; links /how-we-know#curse and #fund; we pick nothing); "make up a number" and a figure asked in a unit we hold no evaluator figure in get figure_request first (we never make up or convert a number; the figure we have, with its unit; since wave 60 a question naming a DALY, WELLBY or GiveWell "x" adds units_defined: each unit defined verbatim in WHO's, HLI's or GiveWell's words with source_url, conversion declined, explore_the_judgment (HLI's own compare-philosophies tool, verbatim, no figure), links /how-we-know#units; with no charity named it is the whole answer, no shortlist). Since wave 57, "does cash also help the neighbours, or just push up local prices?" and "a small trial worked: will it work across a whole country?" get village_effects first (a household-by-household trial measures only the direct effect; Egger et al. 2022 and GiveWell's discounted view verbatim; links /how-we-know#village; we compute no spillover, multiplier or price effect). Since wave 58, a pilot taken national ("how much of that 30% should I expect?") gets kind scale, "through governments or its own programmes?" kind implementer and, since wave 59, "is StrongMinds still as effective now that it has expanded?" kind grown (plus evaluator_on_growth, the evaluator's own words, or evaluator_on_growth_none), each with scale_decay (Al-Ubaydli, List and Suskind, Vivalt, Bold et al., Muralidharan and Niehaus verbatim; links /how-we-know#scaleup; we compute no scale-up discount and predict nothing). Since wave 61: 'keep helping after I stop giving?' / 'most lasting impact?' carry durable_good (the sources' own words on how long effects last, #longrun; no duration or ranking of ours) and 'GiveWell and HLI disagree about X: who is right?' carries evaluators_disagree (each evaluator's dated words side by side; we pick no side). Since wave 62 (theory T18): 'which model should I trust?', 'how do I weigh that kind of uncertainty?' and 'which charity would every evaluator agree on?' carry many_models (the #models rule: act on what holds under every model; GiveWell's cluster-thinking and Ellsberg's ambiguity words verbatim with source_url; our_list says how many listed charities carry more than one evaluator's designation; no score, no blended figure, no side picked); evaluators_disagree now links /how-we-know#models. Since wave 65 (parity with decision_brief): 'can I trust a charity's own report or figures?' / 'is GiveWell (or this site) biased?' carry who_benefits (the #interest rule in Kunda's and the Cochrane review's words; our own stake), and 'is giving locally better than overseas?' carries local_or_overseas (GiveWell's own words; local charities not covered); since wave 86 'my local food bank or GiveDirectly?' (a local organisation against a named charity we cover) carries local_vs_named first (we can speak to one side; GiveWell's words; values line; results unchanged); each opens the answer, and with no charity named results is empty (a method answer lists no charity). Since wave 66: 'what are the main ways an impact estimate can be wrong?' / 'which direction would before-and-after numbers mislead?' carry threat_map (every trap on /how-we-know#threats, the verdict-chain link it breaks and which way it pushes; traps the question names first; no figures) and results is empty. Since wave 69, 'what should I check first, and which section of your method explains it?' carries verdict_chain (the eight links L0-L7 in checking order, each with the /how-we-know sections that test it; results empty), and two or more named charities with no other fixed answer carry compare (a lead, the GET /v1/compare url and compare_charities; units_differ when the units differ; no winner). Since wave 94 (theory T35), "most charity programmes fail when they scale up, so why give at all?" gets village_effects kind failed (named failures verbatim: Bold et al., Cristia et al., FRONTLINE/World; a list of failures has no failure rate; the one full count we hold, IES-commissioned US education trials, in its own words; scale_decay.failed_at_scale; links /how-we-know#atscale; we compute no failure rate and hold no count for charity programmes). Since wave 96: a question about a watchdog's stars that names one listed charity or asks which listed charities have them ("which of yours have four stars on Charity Navigator?") carries rater_answer first (we carry no watchdog ratings, watchdog_marks_carried: false; Charity Navigator's own eligibility and four-star words verbatim; never treated as a charity's name); a gift in a will (bequest, estate) carries give_now_or_wait with bequest (no one can say which charity will be a good pick decades ahead; how to let the gift follow the evidence; no tax, legal or estate advice); "is A really better than B, or is the gap just noise?" carries gap_check first (GiveWell's own words on using its estimates for large differences, verbatim; the #gap test at /how-we-know#gap; we compute no probability, interval or order for any real pair; two named charities keep their figures, none means kind method and no shortlist). Since wave 97 (theory T39): "has X been replicated by independent teams?" or "how many studies support it?" carries replication_status first (the #replicate rule: a second study counts only when independent; ask_these; Camerer et al. 2018 and Turner et al. 2008 verbatim in sources_say; we count no studies and grade no evidence; links /how-we-know#replicate; one named charity keeps its figures, none means kind method, with the evaluator's own cause_challenge words where we hold them). Since wave 98 (theory T37), "if others also fund it, how much of the result is mine?" or "who gets the credit?" carries credit_share first (#mine: the counterfactual for deciding, shares that add up for describing credit; GiveWell's words verbatim; we compute no share of credit and no counterfactual value; one named charity keeps its figures, none means kind method). Since wave 99, "will a program that worked in Kenya work in Ethiopia too?" or "would it work in my country?" carries transport_check first (#transport: how the places differ, re-weighting and its limit, who runs it; Pearl-Bareinboim and Vivalt verbatim; we compute no adjustment for any place; one named charity keeps its figures, none means kind method). Since wave 100, transport_check also carries calculator (#calc-transport, illustrative re-weighting with its limit) and also answers "if it cut deaths 20% in Kenya, how much would it cut them in Nigeria?"; a trust or bias challenge ("your site is effective-altruism propaganda, why should I trust you?") carries trust_challenge (kind method: who we follow, what we never do, how to check us, what we leave out, other lenses to cross-check); and a controversy or criticism ask about a charity where both evaluators published on a disagreement (StrongMinds) carries evaluators_disagree after the status answer, in their own words.

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_orgs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoThe donor's question or a charity name in their own words (same as GET /v1/search?q=). Fixed answers (answer_first, request_declined, scam_answer and the rest) read q and intent alike.
causeNo
intentNo
outcomeNolives_saved | wellbeing_wellbys | health_dalys | income

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "The donor's question or a charity name in their own words (same as GET /v1/search?q=). Fixed answers (answer_first, request_declined, scam_answer and the rest) read q and intent alike.",
      +  "examples": [
      +    "Is Against Malaria Foundation still a good bet?"
      +  ],
      +  "maxLength": 256,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, and the description still adds substantial behavioral context: empty results carry coverage, partial results carry partial_coverage, answer_first ordering, and the request_declined guarantees for scores and averages. It discloses the exact contract of the response shape, which is far beyond what readOnlyHint/idempotentHint convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a multi-thousand-word wall of undifferentiated prose in which release metadata ('Since wave 52', 'Since wave 94 (theory T35)') and internal field names consume space without helping an agent decide anything. Only the first sentence is genuinely front-loaded; the remainder is a changelog fused with a spec, and structure collapses entirely after the opening.

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 tool with no output schema and a highly conditional response contract, the description does cover what comes back under nearly every question class, which is the completeness burden this tool actually carries. It falls short of 5 because the coverage is delivered as an unordered enumeration of internal flags rather than a coherent return-value model an agent could reason over.

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 50%, and the description only implicitly maps its opening phrase to three of the four parameters (cause, outcome family, donor intent phrase), adding no per-parameter detail such as format, enum values, or interaction between q and intent. With q and outcome partially documented in the schema itself, this lands at the baseline for a half-covered schema rather than compensating for the gap.

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 opening sentence states a specific verb and resource ('Heuristic search by cause, outcome family, or donor intent phrase') and immediately distinguishes it from recommend_charity for ranked 'best for outcome' results. The core purpose is therefore easy to extract, though it is buried under an enormous routing appendix rather than being allowed to stand as the headline.

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 names a concrete alternative and the condition that selects it ('Prefer recommend_charity when the user wants ranked best-for-outcome results'), and later routes multi-charity comparisons to compare/compare_charities and method questions to verdict_chain. What holds it below 5 is that the bulk of the guidance is answer-shaping rules for internal response fields rather than a clean when-to-use/when-not-to-use statement an agent can scan.

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