Skip to main content
Glama

Mindful Give Charity Finder

Find charities

find_charities
Read-onlyIdempotent

Search the charities that take gifts on Mindful Give by name. Returns each match with its giving page URL to hand to the donor. This tool only looks charities up and returns a link: it never takes a payment. The donor completes the gift themselves on the charity's giving page, and the charity issues the official tax receipt.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many charities to return (1-10, default 5).
queryYesPart of the charity's name, e.g. "Sacred Heart".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the tool never takes a payment, the donor completes the transaction elsewhere, and the charity issues the tax receipt. That boundary is useful and non-obvious, though it is restated in two sentences.

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 opening sentence front-loads the action and the second delivers the return value, with zero filler. The payment disclaimer is repeated across two sentences ("never takes a payment" then "donor completes the gift themselves"), which is mild redundancy but arguably reinforces a key scope boundary.

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 correctly compensates by stating what a result contains (match plus giving page URL). Combined with full schema coverage and rich annotations, an agent has enough to call this correctly; only the relationship to the get_charity sibling is left unstated.

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%, with both query and limit documented including an example and bounds, so the schema carries the parameter burden. The description only echoes that matching is by name and adds no syntax or interpretation beyond what the schema already says, making the baseline 3 appropriate.

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 gives a specific verb and resource ("Search the charities... by name") and states the return payload (each match plus its giving page URL). It is clear what the tool does, though it does not explicitly distinguish itself from the sibling get_charity beyond the name-search framing.

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 rather than spelled out: the agent learns the result is a link to hand to the donor, who completes the gift on the charity's page. There is no explicit when-to-use vs when-not, and no mention of the get_charity alternative for looking up a single known charity.

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