Skip to main content
Glama

Search the civil-society library

search_library
Read-onlyIdempotent

Search the hangel civil-society library: legislation, document templates, data and research summaries, academic articles, social impact inventory, books, films and glossary.

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

Input Schema

NameRequiredDescriptionDefault
sortNo"relevance": title matches first (default); "title": alphabetical.relevance
limitNoMaximum number of results in this page (default 20, 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.
sectionNoSection slug (listed in platform_info or in the sections field of an earlier search_library result).

Output Schema

NameRequiredDescriptionDefault
asOfNoTime the statuses and dates were evaluated (ISO 8601).
sortYesSort order used.
itemsYes
queryNoPresent when a query was given.
totalYesNumber of matching records (all pages).
offsetYesPosition of the first record of this page in the full result.
hasMoreYestrue when more records follow; call again with nextCursor.
returnedYesNumber of records in this page.
sectionsNo
nextCursorYesOpaque cursor for the next page, or null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results (default 20, at most 50)."New value: +"Maximum number of results in this page (default 20, at most 50)."
    • 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."
    • addedInput schema / properties / sort
      Added value: +{
      +  "default": "relevance",
      +  "description": "\"relevance\": title matches first (default); \"title\": alphabetical.",
      +  "enum": [
      +    "relevance",
      +    "title"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "asOf": {
      +      "description": "Time the statuses and dates were evaluated (ISO 8601).",
      +      "type": "string"
      +    },
      +    "hasMore": {
      +      "description": "true when more records follow; call again with nextCursor.",
      +      "type": "boolean"
      +    },
      +    "items": {
      +      "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"
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "section": {
      +            "type": "string"
      +          },
      +          "sectionSlug": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "Public page of the record on hangel.org.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "title",
      +          "section",
      +          "sectionSlug",
      +          "url",
      +          "contentLanguage"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "nextCursor": {
      +      "description": "Opaque cursor for the next page, or null on the last page.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "offset": {
      +      "description": "Position of the first record of this page in the full result.",
      +      "type": "integer"
      +    },
      +    "query": {
      +      "description": "Present when a query was given.",
      +      "properties": {
      +        "expansion": {
      +          "description": "Query terms that were matched across languages through the hangel multilingual dictionary, and the forms searched in the content.",
      +          "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": {
      +          "description": "The query after case, accent and punctuation normalisation (the raw query is not echoed).",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "normalized",
      +        "expansion"
      +      ],
      +      "type": "object"
      +    },
      +    "returned": {
      +      "description": "Number of records in this page.",
      +      "type": "integer"
      +    },
      +    "sections": {
      +      "items": {
      +        "properties": {
      +          "slug": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "title"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "sort": {
      +      "description": "Sort order used.",
      +      "type": "string"
      +    },
      +    "total": {
      +      "description": "Number of matching records (all pages).",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "offset",
      +    "returned",
      +    "hasMore",
      +    "nextCursor",
      +    "sort",
      +    "items"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"En çok sonuç sayısı (varsayılan 20)."New value: +"Maximum number of results (default 20, at most 50)."
    • addedInput schema / properties / query / description
      Added value: +"Search phrase. Turkish or English."
    • changedInput schema / properties / section / description
      Previous value: -"Bölüm kısa adı (platform_info ya da önceki search_library yanıtındaki sections listesi)."New value: +"Section slug (listed in platform_info or in the sections field of an earlier search_library result)."
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds nothing behavioral beyond that — no mention of pagination behavior, result ordering semantics, or the fact that results are paged via cursor, all of which live only in the schema.

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?

A single front-loaded sentence with zero filler; the content enumeration is dense but each item earns its place by telling the agent what corpora are searchable.

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?

An output schema exists so return values need not be described, and the schema fully documents the parameters. What remains missing is only the comparative routing guidance against sibling search tools, which keeps it from a top score.

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%, so all five parameters (query, section, sort, limit, cursor) are already documented in the schema with defaults, bounds and enum meanings. The description contributes no additional parameter meaning, which is acceptable given the schema carries the full load.

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 names a specific verb ("Search") and resource ("the hangel civil-society library") and enumerates the content types covered — legislation, templates, research summaries, articles, books, films, glossary. That makes the scope concrete and distinguishable from a generic search tool, though it never explicitly contrasts itself with the sibling `search` tool.

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 only implied: the content-type list suggests when to reach for this tool (looking for library material) but there is no explicit when-to-use, when-not, or pointer to alternatives such as `search` or `search_ngos`. An agent must infer the routing condition on its own.

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