claimbase
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 |
|---|---|
| recallA | Answer a question from the claim graph. PASS THE QUESTION, NOT KEYWORDS. Phrasing carries meaning the ranking uses: "why is X still pending" is a question about mechanism and wants a durable explanation, while "is X still the current path" is about currency and wants the newest practice. Reduced to "X pending" both look identical and the wrong claims win. Full questions retrieve at least as well here — this is not a keyword index. Returns claims ranked by epistemic standing — similarity, provenance, currency, and whether a claim superseded others — each with its source, kind, assertion date, and the intent the question was read as. as_of: ISO date. Answers as the graph stood then ("what did I believe in June?"). intent: override if the reading looks wrong — mechanism | current | historical | neutral. |
| timelineA | How belief about a subject changed over time. Matching claims in assertion order, showing which superseded which. Use when an answer may have changed rather than merely being unknown. |
| conflictsB | Open contradictions the compiler could not settle. Empty is the normal state. |
| statsB | What the corpus contains: counts by source, kind and trust. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct concern: recall for answering questions, timeline for temporal evolution, conflicts for unresolved contradictions, and stats for corpus overview. There is negligible overlap because recall returns ranked claims, while timeline explains changes and conflicts lists unresolved issues.
The names are short, lowercase, and readable, but there is no uniform convention: 'recall' is a verb, while 'timeline', 'conflicts', and 'stats' are nouns. This mixed style is still clear and memorable, so it is not chaotic, but it lacks the consistent verb-noun pattern seen in highly coherent tool sets.
Four tools is an appropriate scale for a read-only claim graph query server. Each tool covers a distinct mode of interaction without redundancy, and the count is well within the ideal range for a focused server.
The core workflows are covered: querying (recall), temporal analysis (timeline), contradiction handling (conflicts), and statistics (stats). Minor gaps exist, such as no way to list all claims or fetch a claim by ID directly, but these are workarounds that do not severely hinder the intended use.