DPOLens
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_policiesA | Search the privacy law this community version holds. Call this before writing or changing code that collects, stores, logs, shares or deletes personal data, and before answering a question about what the law requires. What comes back is the clause itself, word for word, with the key, document and version to cite it by. Questions asked here are kept 30 days, with nothing about who asked. |
| get_clauseA | Read one clause by its key, with where it sits and what sits beneath it. Use it when a search result points at another clause, or when you need the whole of an article rather than the part that matched. The call is recorded, with the key that was read rather than a question. |
| list_documentsA | List the laws this community version can cite, and which version of each is in force. |
| get_documentA | Read one document and its top level structure, without the text. The outline is where to find a clause key when you know roughly where to look. Read the words with get_clause. The call is recorded. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| policy_check | Review the change you are working on against the policies and the law. |
| policy_tour | Demonstrate this DPOLens instance with a few real searches. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct retrieval shape: query-based search, key-based clause read, document listing, and document outline read. The only near-pair is get_clause vs. get_document, but the descriptions explicitly disambiguate by stating one returns words and the other returns structure without text.
All four tools follow a clean verb_noun snake_case pattern (search_policies, get_clause, list_documents, get_document). The verbs match the operation type precisely, with no mixed conventions.
Four tools is well within a sensible range and each maps to a necessary step in a read-only legal-lookup workflow: discover documents, browse outline, search, and read a clause. Nothing feels padded or missing for the scope.
The read-only surface covers the core loop of search → locate → read clause, plus document/version discovery. Minor gaps remain: no way to request a specific historical version of a clause, and get_document only exposes top-level structure, forcing extra get_clause calls for deep article traversal.