Skip to main content
Glama
Sign In

Niels Langereis

by com.nielslangereis
OverviewDiscussionsAdmin

Search Niels Langereis's essays

search_essays
Read-onlyIdempotent

Search the essays of Niels Langereis on AI adoption, organisational change, the politics of AI, junior formation and judgement, brand and AI agents, boards and governance. Returns titles, dates, summaries, a matching snippet and links. For a plain list of every essay use list_essays. Follow up with get_essay for the full text before quoting him.

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

Input Schema

NameRequiredDescriptionDefault
queryNoTopic or question, e.g. 'who owns AI decisions', 'brand lock-in by AI agents'. Empty lists everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read. The description adds value beyond that by disclosing the return shape (titles, dates, summaries, matching snippet, links), which tells the agent it gets snippets but not full text. It stops short of a perfect score because ranking, result-count limits, and pagination behaviour are unstated.

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?

Two sentences, front-loaded with the searched domain and immediately followed by the sibling-routing instruction. Every clause carries information; nothing is repeated or padded.

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 single-parameter, read-only search tool with no output schema, the description covers what is searched, what comes back, what it does not return (full text), and which tools to chain for those needs. Nothing an agent requires to invoke it correctly is missing.

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 coverage is 100% and the single query parameter is fully documented, including the empty-string-lists-everything behaviour. The description adds no syntax, phrasing, or formatting guidance beyond what the schema already carries, so the baseline 3 applies.

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") against a specific resource ("the essays of Niels Langereis") and scopes it with a concrete topic list covering AI adoption, governance, brand, etc. It also explicitly separates itself from list_essays, so an agent can route between the two without opening a schema.

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?

Names both alternatives and the condition that selects each: list_essays for a plain full list, get_essay for full text before quoting. This is explicit when-to-use and when-to-switch guidance rather than implied usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Niels Langereis toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources