Skip to main content
Glama

Search hangel

search
Read-onlyIdempotent

Search everything public on hangel (NGOs, events, volunteering, open funding calls, stores, products, library, platform pages) by keyword, in Turkish or English or any other hangel language. Returns matching records with ids for the fetch tool; nextCursor gives further results.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results in this page (default 25, at most 50).
queryYesSearch phrase. Turkish or English, or German, Spanish, French, Arabic, Russian, Persian, Azerbaijani, Hungarian, Hausa or Danish.
cursorNonextCursor from the previous call of this tool, to get the next page. Other arguments can be omitted; if given, they must match that call.

Output Schema

NameRequiredDescriptionDefault
queryNo
totalYesNumber of matching records (all pages).
hasMoreYes
resultsYes
nextCursorYesOpaque cursor for the next page, or null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "nextCursor from the previous call of this tool, to get the next page. Other arguments can be omitted; if given, they must match that call.",
      +  "maxLength": 2000,
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 25,
      +  "description": "Maximum number of results in this page (default 25, at most 50).",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Search phrase. Turkish or English."New value: +"Search phrase. Turkish or English, or German, Spanish, French, Arabic, Russian, Persian, Azerbaijani, Hungarian, Hausa or Danish."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "hasMore": {
      +      "type": "boolean"
      +    },
      +    "nextCursor": {
      +      "description": "Opaque cursor for the next page, or null.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "query": {
      +      "properties": {
      +        "expansion": {
      +          "items": {
      +            "properties": {
      +              "concepts": {
      +                "items": {
      +                  "type": "string"
      +                },
      +                "type": "array"
      +              },
      +              "searchedAs": {
      +                "items": {
      +                  "type": "string"
      +                },
      +                "type": "array"
      +              },
      +              "term": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "term",
      +              "concepts",
      +              "searchedAs"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "normalized": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "normalized",
      +        "expansion"
      +      ],
      +      "type": "object"
      +    },
      +    "results": {
      +      "items": {
      +        "properties": {
      +          "contentLanguage": {
      +            "description": "BCP 47 code of the language the text fields are written in, as stored on hangel (for example \"tr\" or \"en\"); \"und\" when it cannot be determined. Texts are not machine-translated unless \"translated\" is true.",
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "Pass to the fetch tool.",
      +            "type": "string"
      +          },
      +          "snippet": {
      +            "type": "string"
      +          },
      +          "status": {
      +            "description": "For events, volunteering and funding calls: the status of the record (see the list tools).",
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "description": "ngo, event, volunteering, fund, store, product, library or page.",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "Public page of the record on hangel.org.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "title",
      +          "url",
      +          "type",
      +          "snippet"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "Number of matching records (all pages).",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "results",
      +    "total",
      +    "hasMore",
      +    "nextCursor"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Arama ifadesi (TR ya da EN)."New value: +"Search phrase. Turkish or English."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds public-only scope, returned ids for the fetch tool, and nextCursor pagination behavior, which goes beyond the annotations without contradicting them.

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?

The description is a single dense but front-loaded sentence that states purpose, scope, languages, return linkage, and pagination. The parenthetical enumeration and language note earn their place, and there is no filler.

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 an output schema and annotations present, the description supplies enough context about public scope, languages, result ids for fetch, and pagination. The main remaining gap is explicit routing relative to the specialized search and list siblings.

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 the schema already documents query languages, limit, and cursor. The description's mention of keyword and language search largely restates the schema and adds no syntax or format detail beyond it.

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 specific verb, 'Search,' and a clear resource, 'everything public on hangel,' with enumerated content types and keyword/language scope. It is clear this is a cross-domain search, though it does not explicitly name or contrast with sibling searches such as search_library or search_ngos.

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 broad 'everything public' scope implies this is the general search tool, and the mention of ids for fetch suggests a workflow. However, it gives no explicit when-to-use or when-not guidance against specialized search or list_* siblings.

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