Skip to main content
Glama

Mindful Give Charity Finder

Get a charity

get_charity
Read-onlyIdempotent

Get one charity's public details (name, legal name, location, short description, whether it issues tax receipts) and its giving page URL, by its slug (from find_charities). 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": {
      "slug": "<slug>"
    },
    "name": "get_charity"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe charity's slug, as returned by find_charities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered; the description then adds genuinely new behavior: the tool never takes a payment, only returns a link, and the donor completes the gift on the charity's giving page with the charity issuing the receipt. That prevents an agent from misrepresenting the tool as a donation mechanism, which no annotation conveys.

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?

Purpose and returned fields are front-loaded in the first sentence, and the payment disclaimer is placed immediately after as the key constraint. The closing clause about the charity issuing the official tax receipt is slightly redundant with the earlier "whether it issues tax receipts" but reinforces the agent's downstream messaging.

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

Completeness5/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 burden of describing the return shape, and it does so by naming each returned field plus the giving page URL. Combined with the no-payment constraint, an agent has everything needed to call it and to explain the result to a user.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains the slug and its provenance from find_charities. The description restates the same provenance and adds no new syntax or format detail, making the baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb+resource ("Get one charity's public details") and enumerates the returned fields (legal name, location, description, tax-receipt status, giving page URL) plus the keying parameter. It is unmistakably distinct from the sibling find_charities, which is identified as the slug's source.

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 tells the agent this is a lookup by slug obtained from find_charities, which implicitly routes search-style queries to the sibling. It also rules out a plausible misuse (taking a payment). It stops short of an explicit "use find_charities when you don't already have a slug" exclusion, so a 4 rather than a 5.

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