Skip to main content
Glama

Search entries

search_entries
Read-only

Search the entries as the site search does: words match titles, subtitles and descriptions; a Wikidata QID finds the entries linked to it; a VHID finds that entry and the entries that link to it.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
offsetNo

Output Schema

NameRequiredDescriptionDefault
limitNoThe page size used: the `limit` asked for, clamped to the endpoint’s range.
queryYesThe query as it was read: trimmed and cut to 100 characters.
totalYesHow many entries matched in all.
offsetNoThe offset used: the `offset` asked for, clamped to 0–10,000.
resultsYesBest match first.
next_offsetNoThe `offset` of the next page, or null when this is the last one. Follow it rather than computing it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / results / items / properties / thumb_plate
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "light",
      +        "dark",
      +        "none"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The plate `thumb` is drawn on (the lead image’s `plate`), and always null when `thumb` is. `light` or `dark`: a picture with transparent pixels (a logo, most often), drawn on a plate of that colour so its ink shows in light and dark mode alike. `none`: an opaque picture (a photo), drawn as it is, with no plate. Null while the site has not yet looked at its pixels: decide from the picture itself, as the site’s pages then do."
      +}
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "vhid",
      -  "short",
      -  "title",
      -  "subtitle",
      -  "verified",
      -  "claimed",
      -  "entity_kind",
      -  "thumb",
      -  "snippet",
      -  "highlighted",
      -  "url"
      -]New value: +[
      +  "vhid",
      +  "short",
      +  "title",
      +  "subtitle",
      +  "verified",
      +  "claimed",
      +  "entity_kind",
      +  "thumb",
      +  "thumb_plate",
      +  "snippet",
      +  "highlighted",
      +  "url"
      +]
  2. Changed4 schema fields changed
    • addedOutput schema / properties / results / items / properties / claimed
      Added value: +{
      +  "description": "The person or organisation the entry is about has claimed it. Never who.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / results / items / properties / entity_kind
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "person",
      +        "musical_group",
      +        "sports_organization",
      +        "broadcaster",
      +        "publisher",
      +        "educational_institution",
      +        "research_organization",
      +        "religious_organization",
      +        "museum",
      +        "financial_institution",
      +        "chain",
      +        "nonprofit",
      +        "company",
      +        "organization",
      +        "show",
      +        "website",
      +        "software",
      +        "brand"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The finer kind of thing it is, from its Wikidata item’s classes; null when unknown (an organisation or a brand not yet read since kinds were added reads null until the sync next reads its item). Each kind belongs to one `entity_type`, and `person`, `organization` and `brand` are also the kinds of an entry of that type with no finer one. The kinds, with their type: `person` (person: person), `musical_group` (organization: musical group), `sports_organization` (organization: sports organisation), `broadcaster` (organization: broadcaster), `publisher` (organization: publisher), `educational_institution` (organization: educational institution), `research_organization` (organization: research organisation), `religious_organization` (organization: religious organisation), `museum` (organization: museum), `financial_institution` (organization: financial institution), `chain` (organization: retail or hospitality chain), `nonprofit` (organization: charity or non-profit), `company` (organization: company), `organization` (organization: organisation), `show` (brand: show), `website` (brand: website or app), `software` (brand: software), `brand` (brand: brand). New kinds may be added; treat an unknown value as its `entity_type`."
      +}
    • addedOutput schema / properties / results / items / properties / thumb
      Added value: +{
      +  "description": "The lead image at the width a list row draws it (100 CSS pixels), as a path on the site: the width the image is really served at (200 for a Commons picture), never one that redirects. Null when there is no image.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "vhid",
      -  "short",
      -  "title",
      -  "subtitle",
      -  "verified",
      -  "snippet",
      -  "highlighted",
      -  "url"
      -]New value: +[
      +  "vhid",
      +  "short",
      +  "title",
      +  "subtitle",
      +  "verified",
      +  "claimed",
      +  "entity_kind",
      +  "thumb",
      +  "snippet",
      +  "highlighted",
      +  "url"
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add meaningful behavior: which fields words match against, and that QID/VHID searches traverse links rather than matching text. It says nothing about result ordering, pagination limits, or the cap of 50 results.

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?

One front-loaded sentence that defines the tool by analogy ("as the site search does") and then enumerates the three input forms. No filler and no repetition of the schema.

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 shape needn't be described, and the read-only annotation covers safety. The only material gap is pagination behavior, since limit and offset are unbounded in the description despite a 50-result cap in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for query, and it does that well by enumerating the three accepted query forms. The limit and offset parameters get no mention at all, so pagination semantics are undocumented in both places.

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?

A specific verb plus resource ("Search the entries") with the matching semantics spelled out, which tells an agent exactly what kind of lookup this performs. It does not name the neighboring get_entry/get_entries tools, so the distinction from exact-lookup siblings is left implicit.

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 three query modes implicitly define when to use it (word search, known QID, known VHID), which is real guidance for choosing an input form. However, it never states how this differs from get_entries or get_entry, so an agent must infer the boundary from sibling names alone.

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.