Robert Blust
Server Details
Robert Blust: One model, true everywhere
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes, and the descriptions actively cross-reference each other (e.g. fetch vs get_entity, list_entities vs search, list_rules vs describe_rule). There is mild overlap among the relation-surfacing tools — describe_relations, describe_schema and list_references all expose edges — but the descriptions draw sharp scope boundaries (whole vocabulary vs one type vs filtered edges) so an agent can select correctly.
Strong verb_noun pattern: describe_errors, describe_relations, describe_rule, describe_schema, list_checks, list_entities, list_references, list_rules, list_types, get_entity, find_evidence. Only fetch, search and diagram break the pattern with bare verbs/nouns, but they are few and still readable.
Fourteen tools sit comfortably in the well-scoped range for a model-browsing server, and each maps to a distinct facet (types, schemas, relations, rules, checks, references, evidence, diagrams, error contracts). No obviously redundant or padding tools.
For a read-oriented vocabulary/model viewer the surface is thorough: discovery (list_types, describe_schema, describe_relations), retrieval (get_entity, fetch, search, list_entities, list_references), conventions (list_rules, describe_rule), gate checks, diagramming and a refusal contract. The only gap is that the surface is entirely read-only — no mutation/authoring operations — which is likely by design but limits lifecycle coverage.
Available Tools
14 toolsdescribe_errorsARead-onlyInspect
What a refused call looks like. A tool's output schema covers its answers only, so use this once, to branch on refusals or validate them. No input. Returns errors, every code with when it is raised and the JSON Schema of its details, and schema, the JSON Schema of a whole refusal: error with code, message, rule, details, beside model.
Inputs: no named parameters. Returns: model, errors, schema
describe_relationsARead-onlyInspect
What the schemas declare between types: references with form and cardinality, ownership, enums, joins, list kinds. Use for a diagram or audit; for one type's full schema use describe_schema. Optional type narrows every list, direction (declares, declared-to, both; needs type) one side of relations, via relations and enums. Returns those lists, with forms and reading explaining every term. Not paged.
Inputs: via, type, direction. Returns: enums, forms, joins, lists, +4 more
describe_ruleARead-onlyInspect
One convention of the vocabulary as written, not a company's own rule (an entity of type rule: list_entities, get_entity). Input: rule, a number from list_rules such as R9, in either case. Returns rule, title, part, text and the file's url. An unknown number is refused with the known ones listed.
Inputs: rule (required). Returns: url, part, rule, text, +2 more
describe_schemaARead-onlyInspect
One type's schema: its sections as written and its declared relations as data. Use to learn what an entity of the type may hold; for the whole vocabulary use describe_relations. Input: type. Returns url, the schema's own file, sections, and relations: owner, owns, references both ways, enums, joins and lists.
Inputs: type (required). Returns: url, name, type, model, +3 more
diagramARead-onlyInspect
A picture of the model as Mermaid; edge data: list_references. Input: shape; id, domain, type or unit narrow it. aggregate, flow, lifecycle take a context's id; organization without id draws the company; system a landscape, holds its data; usecase, scenario a use case's; requirements a feature's, product's, use case's or requirement's. Returns mermaid, nodes, links, units, counts. Max 50 nodes.
Inputs: shape (required), id, type, unit, +1 more. Returns: unit, actor, edges, links, +11 more
fetchARead-onlyInspect
One entity's page as written. Use to quote or display the source; for structured fields and references use get_entity. Input: id or address, from search, list_entities or any reference. Returns id, title, type, url and text, the Markdown source. Takes no name: search with match "name" finds the id.
Inputs: id (required). Returns: id, url, text, type, +2 more
find_evidenceARead-onlyInspect
Every edge into one skill, grouped by the type of the page that drew it. Use to check a claimed skill against its evidence. Input: skill, an id, canonical name or address; optional limit, cursor. Returns skill, evidence and page; a profile's claim arrives via Skills.Skill with its level, an evidence row via Evidence.Skill. Attributes are verbatim.
Inputs: skill (required), limit, cursor. Returns: page, model, skill, evidence
get_entityARead-onlyInspect
One entity as structured data: fields, sections, tables, references both ways. Use to reason over one; for its page as written use fetch. Input: id or address, where its page sits, or type and name; an ambiguous name is refused with candidate ids. Returns entity, by id. Reference lists hold at most 50 edges; referenceCounts gives totals, list_references the rest.
Inputs: id, name, type. Returns: model, entity
list_checksARead-onlyInspect
The checks the model's own gate runs, from the checker release this server was built with. Use to see which rules a script enforces and which are left to a reader. No input. Returns checks, each with name, rule, title and what it reports, a failure or a note that fails nothing, and ranBy. This server runs none of them.
Inputs: no named parameters. Returns: model, ranBy, checks
list_entitiesARead-onlyInspect
Entities with their frontmatter's short facts, in address order or newest first. Use to browse, or for what runs on a date, came last or has a value; to find by words use search. Input: optional type, owner, order, on, by, where, fields, limit, cursor. Returns entities with fields, and page; follow page.nextCursor while page.hasMore.
Inputs: by, on, type, limit, +5 more. Returns: page, type, model, entities
list_referencesARead-onlyInspect
The model's edges, filtered and paged. Use to inspect one entity's relations or one kind of reference without taking whole entities. Optional entity (an id or address), direction (out, in, both; needs entity), via, type (the far end's type, or either end's without entity), limit, cursor. Returns edges, each from, via, to, attrs, and page.
Inputs: via, type, limit, cursor, +2 more. Returns: page, edges, model
list_rulesARead-onlyInspect
The vocabulary's conventions the model is held to, R0 onwards, from its core's CONVENTIONS.md. Use to resolve a number a schema or refusal cites, such as R9. A company's own rules are entities of type rule: list_entities and get_entity. No input. Returns tagline, the file's url, and rules, each with rule, title and part; describe_rule gives one rule's text.
Inputs: no named parameters. Returns: url, model, rules, tagline
list_typesARead-onlyInspect
Every type the model's schemas declare. Use first, to learn which types exist before listing or describing one. No input. Returns types, each with type, name, tagline, owner (the type it nests under, or null) and count, the entities it holds.
Inputs: no named parameters. Returns: model, types
searchARead-onlyInspect
Find entities by words, substring or exact name. match: "words" needs every query word's stem in name, tagline, fields, sections or cells; "text" (default) is a case-insensitive substring over the same; "name" the exact canonical name. Optional type, owner, limit, cursor. Returns results with id, title, type, matched, words in words mode, and page: name matches first, then a listing.
Inputs: query (required), type, limit, match, +2 more. Returns: page, match, model, query, +2 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
The immit English and Japanese dictionary: entries, search and inflection tables for an agent
MCP server for classical Chinese texts: sentence lookup, source attribution and full-text search
Pre-registered hypothesis testing by AI agents. First corpus: the book Nature's Memory.
Ancestry on G25 and raw DNA: nMonte fits, PCAs, GEDmatch-style and G25 calculators, qpAdm models.
Related MCP Servers
- AlicenseAqualityBmaintenanceGives AI assistants grounded, sourced access to cross-linguistic data: WALS typological features and Glottolog language classifications. Answers come with provenance, family- and genus-aware counts, and clarification requests instead of guesses when codes are ambiguous.1034 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceEnables querying 10,000 years of historical social-complexity data from the Seshat Global History Databank through 9 tools, allowing counterfactual analysis and comparison of polities in natural language.1-
- AlicenseAqualityBmaintenanceSelf-hosted read-only MCP server over a local library of ancient-text corpora — 2.47M documents and 118M passages from 258 sources (cuneiform, Classical, biblical, medieval and more), with the license class tracked on every passage. 14 research tools: full-text search, concordance, passage display, dictionary definitions, etymologies, cognates, parallel passages, text alignment, place lookup etc146MIT
- AlicenseAqualityBmaintenanceMCP server for the Meta-Consciousness (MCAI) theory: term definitions, concept relations and source citations, served from a local knowledge base.25MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.