Skip to main content
Glama

Nicolas Sitter Research

search_research_articles

Read-only

Search Nicolas Sitter's published research on AI search, answer engines and hotel technology by keyword, matching headlines and descriptions. Use this when the user asks what research exists on a topic, wants studies or data about how ChatGPT/Gemini/Perplexity/Copilot/Google AI Mode behave, asks about AEO/GEO measurement, or asks what this site has written about something. Returns headline, description, URL and publish date for each match; call with no query to list everything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_research_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword or phrase. Omit to list all articles.
clientNoOptional: identify yourself, e.g. "my-agent/1.0". Not required and never used by the tool itself — recorded only so the public tracker at /projects/agent-tools can measure how many callers self-identify when nothing forces them to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds useful behavior: matching is over headlines and descriptions, and the broad no-query behavior lists the entire corpus. It also specifies the returned fields (headline, description, URL, publish date), which matters because there is no output schema. It does not discuss match ranking, case sensitivity, or result limits.

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?

Front-loaded with the action and scope, then usage triggers, then return values — a sensible ordering with little waste. The middle usage sentence is a long enumeration of product names, but each token is a legitimate search trigger rather than filler.

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 and only two optional parameters, the description carries everything needed: what is searched, when to call it, what comes back, and what happens with an empty query. Nothing an agent needs in order to call it correctly is missing.

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, but the description adds real meaning by stating which fields the keyword is matched against (headlines and descriptions) and by restating that omitting the query returns everything. The optional client parameter's purpose is fully explained in the schema itself and needs no further elaboration here.

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?

States a specific verb (Search) plus a precisely scoped resource (Nicolas Sitter's published research on AI search, answer engines and hotel technology) and the matching fields (headlines and descriptions). It also serves the same scope as the sibling tool get_article, making clear this one is a keyword search over a corpus rather than a single-item fetch.

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?

Gives concrete triggering conditions: asking what research exists on a topic, wanting studies or data about specific AI products, asking about AEO/GEO measurement, or asking what the site has written about something. It also explains the no-query case (list everything). It does not name an alternative for retrieving a specific known article, so it falls short of a full when/when-not/alternatives statement.

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