Skip to main content
Glama
What Do They Know

What Do They Know

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WDTK_API_KEYNoEnables create_request_record and update_request_state write tools

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Read WhatDoTheyKnow public JSON, Atom feeds, and CSV exports. Optionally call the experimental write API if configured.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
build_request_urlA

Build a prefilled WhatDoTheyKnow request URL.

get_request_feed_itemsA

Return parsed Atom feed entries for a specific FOI request as structured objects.

Use this instead of reading the raw wdtk://requests/{slug}/feed resource when you want structured AtomEntry objects rather than raw XML. Each entry's link field contains the request URL; use the slug from that URL with get_request_detail for full detail.

get_request_detailA

Return full public JSON for a WhatDoTheyKnow FOI request.

The response includes request metadata, public body details, requester details, state/status fields, and the visible info_request_events array containing correspondence text and attachment metadata where WhatDoTheyKnow exposes it.

get_authority_detailA

Return full public JSON for a WhatDoTheyKnow public authority.

The response includes contact/profile fields, tags, publication links, and request statistics such as successful, overdue, and classified request counts where WhatDoTheyKnow exposes them.

Authority slugs use underscores, not hyphens — e.g. 'home_office' not 'home-office'. Use search_authorities to find the correct slug.

get_user_feed_itemsA

Return parsed Atom feed entries for a user's WhatDoTheyKnow activity.

Unlike the raw wdtk://users/{slug}/feed resource, this returns structured entries with the Atom content converted to readable text in content and mirrored to summary for clients that only display summary fields.

get_user_requestsA

List a user's visible WhatDoTheyKnow requests from their public requests page.

Returns request title, slug, URL, current displayed status, authority, updated timestamp, event text, and the page snippet. status_filter is a case-insensitive substring match against the displayed status.

search_request_eventsA

Search WhatDoTheyKnow's feed-based event index and return structured results.

Call this to find FOI requests matching a query expression. Returns up to limit AtomEntry objects. Use the link field of each result as the next navigation step — extract the request slug and call get_request_detail or get_request_feed_items for full detail.

Example expressions: status:successful body:"Liverpool City Council" (variety:sent OR variety:response) status:successful

search_authoritiesA

Search WhatDoTheyKnow public authorities by name.

Returns up to limit authorities whose name or short_name contains query (case-insensitive). Use the slug field with authority_json or build_request_url as the next step.

Example: search_authorities("Liverpool") → slug "liverpool_city_council" Then: authority_json with that slug, or build_request_url with it.

create_request_recordA

Create a request through the experimental write API.

Requires WDTK_API_KEY in the server environment.

update_request_stateA

Update the user-assessed state of a request through the experimental write API.

Requires WDTK_API_KEY in the server environment.

list_promptsA

List all available prompts.

Returns JSON with prompt metadata including name, description, and optional arguments.

get_promptA

Get a prompt by name with optional arguments.

Returns the rendered prompt as JSON with a messages array. Arguments should be provided as a dict mapping argument names to values.

Prompts

Interactive templates invoked by user choice

NameDescription
draft_foi_requestDraft a narrow, specific FOI request suitable for WhatDoTheyKnow.

Resources

Contextual data attached and managed by the client

NameDescription
all_authorities_csvDownload the complete CSV of every WhatDoTheyKnow public authority. WARNING: this is a large payload — use search_authorities(query) for targeted lookups, or authority_json for a specific body. Only call this when you need the full dataset (e.g. bulk analysis or seeding a list).

TDQS

A4.1/5.0

Scored across 12 tools

Disambiguation4/5

Most tools target clearly distinct resources and actions: request detail vs. authority detail vs. user requests vs. authority search. The main overlap is between feed/event tools that both return AtomEntry-style results, but descriptions clarify which to use. The prompt tools are unrelated to the FOI domain, though not easily confused with the domain tools.

Naming Consistency5/5

All tool names use consistent snake_case and follow a predictable verb_noun pattern: get_*, search_*, build_*, create_*, update_*, list_*. No naming convention mixing is present.

Tool Count5/5

Twelve tools is a well-scoped size for this domain, covering reads, search, URL building, and limited writes. The two prompt tools are somewhat extraneous, but the overall count remains reasonable and manageable.

Completeness4/5

The surface covers the core FOI workflows: request detail/feed, user activity, authority search/detail, event search, URL construction, and experimental create/update operations. Minor gaps remain, such as attachment content retrieval, user profile detail, and richer request lifecycle operations, but agents can work around most of them.

Maintenance

ActivityNo data
ResponsivenessOutdated data