Skip to main content
Glama

Tweedekamer Nl

by io.github.pipeworx-io
OverviewAdmin

Search People

search_people
Read-onlyIdempotent

Convenience search over Tweede Kamer members/people (Persoon entity) by name. Matches a case-insensitive substring against surname (Achternaam) and/or preferred first name (Roepnaam). Returns id, name parts, role (Functie) and party label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMax results (default 25).
nameYesName fragment to search for, e.g. "Rutte", "Mark", "Wilders".
fieldNoWhich field to match: achternaam (surname), roepnaam (first name), or both (default).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "field": "achternaam",
+    "name": "Rutte",
+    "top": 10
+  },
+  {
+    "field": "both",
+    "name": "Wilders",
+    "top": 25
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive hints. The description adds valuable behavioral context: case-insensitive substring matching and the specific fields searched (surname, first name). It also discloses the return fields (id, name parts, role, party label), which is useful because there is no output 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?

The description is succinct, three sentences that cover purpose, matching behavior, and return values. Every sentence adds distinct value with no redundancy or 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?

For a simple search tool with 3 parameters and no output schema, the description is complete: it explains what the tool searches, how it matches, and what it returns. Annotations cover safety, and the schema covers parameter details, so nothing 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 parameters are fully described. The description adds meaning beyond the schema by explaining the matching behavior (case-insensitive substring) and explicitly tying the 'field' parameter to surname/first name, which clarifies how the 'name' parameter is interpreted.

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 clearly states a specific action ('search') over a defined resource ('Tweede Kamer members/people (Persoon entity)') with a specific scope ('by name'). It differentiates from general search tools like 'search_within' by targeting people and specifying matching fields (surname/first name).

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?

The description implies when to use this tool: when you need to find a person by name. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to select it over generic search tools. The 'Convenience search' label signals a specialized wrapper.

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

All Tweedekamer Nl toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources