Skip to main content
Glama
michaelcpattinson-star

claudette

by michaelcpattinson-star
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_corpusA

Find passages across the corpus that bear on a question.

Call this before answering anything of substance, then answer AS Claudette
(see the server instructions: your own voice, view first, no citations in
the body, a Sources: line at the end). Returns ranked passages, each with a
citation `ref` and the query terms it actually contains. Not for reading a
passage you already have a ref for — use read_passage.
read_passageA

Return one passage verbatim, with its neighbours, for quoting or checking a citation.

Use after search_corpus when you need the surrounding text. Not for finding
passages — it takes a ref, not a question.
list_worksA

List works in the corpus: author, title, year, why it is included, source, and slug.

Use to tell the user what the corpus holds, or to pick a slug for a
restricted search. Not a search — it returns no passages. For the full
tier, filter by author; use list_authors to find her name first.
list_authorsA

Find which women are in the corpus and how much of each: name, works, passages, curated.

Use when the user asks 'is X in there?' or 'who do you have on Y?'. Not a
passage search — pair with search_corpus once you know the name.
corpus_provenanceA

State what this corpus is, where it came from, how it was curated, and its known limits.

Use when the user asks what Claudette is, whose words these are, or how the guarantee is enforced.

verify_attributionA

Check against Wikidata that a person exists, is recorded as a woman, and wrote the named work.

Lens mode only: call this BEFORE naming any author or work from memory
rather than from the corpus. `ok` means name her. `weak` means name her
with the stated caveat. `not_found` means do not. Not for authors already
in the corpus — search_corpus is their check. The one network call this
server makes; it goes only to Wikidata.

Prompts

Interactive templates invoked by user choice

NameDescription
claudetteClaudette's standing instructions: answer only from the corpus, cite everything, say when it does not speak to the question.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct job: search_corpus finds passages by question, read_passage retrieves a known ref, list_works/list_authors expose metadata, corpus_provenance explains the corpus, and verify_attribution handles inbound Wikidata checks. The descriptions explicitly warn against cross-use, so an agent should not confuse them.

Naming Consistency4/5

Five of six tools follow a clear snake_case verb_noun pattern (search_corpus, read_passage, list_works, list_authors, verify_attribution). corpus_provenance breaks the pattern as a noun phrase rather than a verb, but the naming remains predictable and easy to skim.

Tool Count5/5

Six tools is well-scoped for a read-only corpus assistant: search, passage lookup, two metadata views, provenance, and verification. Each tool has a clear role and none feels redundant or like filler.

Completeness5/5

The surface covers the full user workflow for this domain: discover works/authors, search passages, read passages verbatim for citation checks, explain corpus provenance, and verify external attributions. No create/update/delete operations are needed because the corpus is curated and read-only.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources