Skip to main content
Glama

Search entity records

search_entities
Read-onlyIdempotent

Searches GMM's researched entity records (people, companies, institutions, places) by name, role or summary. Open a match with get_entity_record. Filter by type slug. Matching is the content store's substring match and accents count, so "Male" does not find "Malé"; search_site folds accents and searches every kind at once. Paginates: when more results remain, the structured answer has a nextCursor (absent on the last page). To continue, call this tool again with the same arguments and cursor set to that value.

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": {
      "q": "<q>"
    },
    "name": "search_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesName or words to look for.
langNoen (English) or dv (Dhivehi).en
typeNoCategory slug, e.g. company or person. list_entity_categories has the slugs in use.
limitNoResults to return (1-25, default 10).
cursorNoContinue a previous result: the nextCursor it returned, unchanged. Only valid with the same other arguments (limit may differ).

Output Schema

NameRequiredDescriptionDefault
totalYesAll matching records, not just this page.
entitiesYes
nextCursorNoOpaque cursor for the next page: pass it back as the cursor argument, with the same other arguments. Absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds matching semantics that the annotations cannot convey: a substring match where accents count ("Male" misses "Malé"). It also discloses pagination behavior end to end, including when nextCursor is absent and the exact procedure for continuing.

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 front-loaded with what the tool searches, then routing, then matching caveats, then pagination, and no sentence repeats another. The telegraphic style ("Filter by type slug.") fits dense reference prose rather than padding.

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?

For a 5-parameter search tool with an output schema, everything an agent needs is present: scope, alternative routes, filter source, match gotchas, and full pagination protocol. Return-value shape is left to the output schema, which is correct.

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 coverage is 100%, so the baseline is 3. The description adds real value beyond the schema by cross-referencing list_entity_categories for valid type slugs and spelling out cursor continuation rules, while the 'q' matching semantics are covered in the prose rather than in the schema.

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 specific verb and resource ("Searches GMM's researched entity records") and enumerates the covered kinds (people, companies, institutions, places). It also distinguishes itself from the sibling tool get_entity_record, which retrieves a single record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

This tool explicitly names two alternatives and the conditions that select them: get_entity_record to open a match, and search_site when you need accent folding across every kind at once. It also names filter-by-type and the list_entity_categories tool that has the slugs in use.

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