Skip to main content
Glama

Tweedekamer Nl

by io.github.pipeworx-io
OverviewAdmin

Query Entity

query_entity
Read-onlyIdempotent

Query a Tweede Kamer (Dutch Parliament) OData v4 entity set with full OData passthrough. Entity names and fields are Dutch. Returns matching records under value. Use $filter to subset (e.g. "Achternaam eq 'Rutte'" or "contains(NaamNL,'Groen')"), $select to pick fields, $orderby to sort, $expand for related records. Always set $top to bound responses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMax records to return (default 25, OData $top).
skipNoRecords to skip for paging (OData $skip).
countNoIf true, include total match count as @odata.count.
entityYesDutch entity name. Common: Persoon (people/MPs), Fractie (parties), Zaak (cases/motions/bills), Activiteit (activities/debates), Vergadering (meetings), Stemming (votes), Besluit (decisions), Document (documents).
expandNoOData $expand: navigation properties to inline, e.g. "FractieZetel".
filterNoOData $filter. eq/ne/gt/lt + contains()/startswith()/endswith(). String literals in single quotes (double an embedded quote). E.g. "Afkorting eq 'VVD'", "contains(Achternaam,'Rut')", "AantalZetels gt 10".
selectNoOData $select: comma-separated Dutch field names, e.g. "Id,Achternaam,Roepnaam,Functie".
orderbyNoOData $orderby, e.g. "Achternaam asc" or "GewijzigdOp desc".

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: +[
+  {
+    "entity": "Persoon",
+    "filter": "Achternaam eq 'Rutte'",
+    "select": "Id,Achternaam,Roepnaam,Functie",
+    "top": 10
+  },
+  {
+    "entity": "Fractie",
+    "filter": "AantalZetels gt 10",
+    "orderby": "AantalZetels desc",
+    "select": "Id,Naam,Afkorting,AantalZetels",
+    "top": 25
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, and the description aligns with these. It adds useful behavioral context such as 'Returns matching records under `value`', 'Entity names and fields are Dutch', and 'Always set $top to bound responses'. It does not describe pagination or error behavior, but the annotations cover the safety profile.

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 compact and front-loaded, with the core purpose in the first sentence. It includes concrete examples and an essential usage caveat without unnecessary filler. Every sentence earns its place.

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?

For an 8-parameter OData passthrough tool with no output schema, the description covers the essential operational context: entity set type, Dutch naming, return location, common query operators, and the need to bound responses. The schema covers parameter details, and annotations cover safety. It could mention paging or entity list more explicitly, but it is sufficiently complete for an agent to use correctly.

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 100%, with detailed parameter descriptions already present. The tool description adds value with concrete OData examples and the emphasized $top guidance, which goes slightly beyond the schema. It does not fully compensate for the absence of an output schema, but for parameter semantics it is solid.

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 the tool queries a Tweede Kamer OData v4 entity set with full OData passthrough. It distinguishes itself from siblings like get_entity_by_id by emphasizing entity-set-level querying and OData options. The scope, resource, and behavior are immediately obvious.

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 provides clear context for typical usage, including $filter, $select, $orderby, and $expand, plus the strong recommendation to always set $top. It does not explicitly name alternatives or state when not to use this tool, but the context is clear enough for an agent to choose it over more specific siblings.

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