Skip to main content
Glama
Sign In

Tweedekamer Nl

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Entity By Id

get_entity_by_id
Read-onlyIdempotent

Fetch one Tweede Kamer record by its GUID id. Pass the entity name and the record Id (a GUID, e.g. "8b3664bd-77e4-468b-af96-f3f4ec27fcce"). Optionally narrow fields with $select or inline related records with $expand.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "8b3664bd-77e4-468b-af96-f3f4ec27fcce",
      "entity": "Persoon",
      "select": "Id,Achternaam,Roepnaam,Functie"
    },
    "name": "get_entity_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecord GUID, e.g. "8b3664bd-77e4-468b-af96-f3f4ec27fcce".
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.
selectNoOData $select, comma-separated field names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "entity": "Persoon",
+    "id": "8b3664bd-77e4-468b-af96-f3f4ec27fcce",
+    "select": "Id,Achternaam,Roepnaam,Functie"
+  },
+  {
+    "entity": "Fractie",
+    "expand": "FractieZetel",
+    "id": "a1b2c3d4-e5f6-47g8-h9i0-j1k2l3m4n5o6"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds minimal behavioral context beyond the schema, mentioning the ability to inline related records via $expand. It doesn't describe return format or error behavior, but for a read-only fetch operation this is acceptable.

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 two sentences, front-loaded with the core purpose, and includes a concrete GUID example and optional parameters. Every sentence earns its place with no redundancy.

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 a simple fetch-by-id tool with well-documented parameters and safe annotations, the description covers the essential usage. There is no output schema, but 'Fetch one record' implies the return. It could mention not-found behavior, but the description is otherwise complete for the tool's simplicity.

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 description coverage is 100%, with each parameter (id, entity, select, expand) already well-documented in the schema. The description adds little beyond what the schema provides, only repeating the GUID example and the purpose of $select/$expand. Baseline 3 is appropriate.

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's purpose: 'Fetch one Tweede Kamer record by its GUID id.' This is a specific verb and resource, and the GUID-based lookup distinguishes it from sibling search tools like query_entity or search_people.

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 direct instructions on how to use the tool: pass the entity name and the record Id, with optional $select and $expand. It gives clear context for usage, though it does not explicitly name alternative tools or state when not to use this tool.

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
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