Skip to main content
Glama
santismm

santismm-knowledge

Official
by santismm
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

Corpus Overview — Start Here

get_overview
Read-onlyIdempotent

Get the complete MCP map: five-domain core plus Article, Labs, Homeric Atlas, claim-registry surfaces, tools, identifiers, citation rules, languages, license, and bulk-ingest URLs.

Instructions

Get the complete MCP map — start here. Returns the five-domain core plus the separate Article, Labs, Homeric Atlas and claim-registry surfaces, with their tools, identifiers, citation rules, languages, licence and bulk-ingest URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bulkYes
nextYes
siteYes
totalYes
corpusYesWhether this copy is current. Compare against the hosted endpoint: a lower total or an older newest_unit means you are holding a snapshot, not that the corpus lacks what you asked for.
sourceYes
domainsYes
licenseYes
localesYes
extensionsYes
license_urlYes
license_spdxYesSPDX id — check this, not the prose.
resource_uriYesRead this same document with resources/read.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv0.4.1
    • addedOutput schema / properties / corpus
      Added value: +{
+  "additionalProperties": false,
+  "description": "Whether this copy is current. Compare against the hosted endpoint: a lower total or an older newest_unit means you are holding a snapshot, not that the corpus lacks what you asked for.",
+  "properties": {
+    "freshness": {
+      "type": "string"
+    },
+    "newest_unit": {
+      "description": "Newest unit date in THIS copy (YYYY-MM-DD).",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "newest_unit",
+    "freshness"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / extensions
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "citation": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "lookup": {
+        "type": "string"
+      },
+      "source": {
+        "type": "string"
+      },
+      "surface": {
+        "type": "string"
+      },
+      "tools": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "surface",
+      "description",
+      "tools",
+      "source",
+      "lookup",
+      "citation"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / resource_uri
      Added value: +{
+  "description": "Read this same document with resources/read.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "source",
-  "site",
-  "locales",
-  "license",
-  "license_spdx",
-  "license_url",
-  "total",
-  "domains",
-  "next",
-  "bulk"
-]New value: +[
+  "resource_uri",
+  "source",
+  "site",
+  "locales",
+  "license",
+  "license_spdx",
+  "license_url",
+  "total",
+  "domains",
+  "extensions",
+  "corpus",
+  "next",
+  "bulk"
+]
  2. First observedv0.2.1

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context by specifying that the tool returns a 'complete MCP map' and listing what that map contains, reinforcing that this is a read-only, non-mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with the key usage instruction front-loaded. Every phrase adds value: the scope, the surfaces, and the included metadata are all packed without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with an output schema, the description is sufficiently complete: it names what the agent receives, why to call it, and where it fits among many sibling tools. It does not detail the output schema's shape, but the presence of an output schema covers that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and an empty input schema, so the schema fully covers parameter semantics. There is nothing more the description needs to explain, and the lack of parameters makes the 'start here' instruction unambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Get the complete MCP map' and says to 'start here.' It further distinguishes the tool by enumerating the five-domain core and four separate surfaces, making its scope clear and different from the many individual get_* and list_* sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'start here' in both the title and description provides clear guidance that this tool is the intended entry point before using domain-specific tools. It does not explicitly list exclusions or alternatives, but for an overview tool this is sufficient context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/santismm/santismm-knowledge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server