Skip to main content
Glama

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_certificationA

Return the certification record for ONE DeepSeek Harness plugin repository, identified by its GitHub owner and repository name: the letter grade, the snapshot date the grade was measured, and the five-dimension evidence behind it. Use this when you already know which plugin you are asking about and need its grade, or the reasoning that produced it. Use list_certified instead to enumerate every certified plugin, and certification_spec instead to learn what the five dimensions, the grade scale and the veto rule mean. Read-only: it reads a registry snapshot bundled with this server. When the public registry is reachable the snapshot may be refreshed opportunistically; otherwise the embedded snapshot is used. It performs no writes, contacts no service other than that optional refresh, and requires no credentials. Two calls with the same arguments return the same record. If the registry holds no entry for that owner/repo, the result is a plain not-found sentence naming the key it looked up and the snapshot date - it never invents, interpolates or approximates a grade.

list_certifiedA

List every plugin in the public dsh-plugin-certification registry, each with its repository, letter grade and snapshot date, plus the registry spec version, its generation timestamp and the total count. The returned coverage object states what that count is and is not: the registry is an opt-in subset of the ecosystem (a plugin appears only after it was evaluated), so a short list — the bundled snapshot holds one entry — is not evidence that the ecosystem is uncertified, and a single-entry list supports no comparison across plugins. Read coverage before drawing any conclusion from count. Use this to discover what is in the registry, or to compare grades across plugins. Use get_certification instead when you already know the plugin and want its full five-dimension evidence; this tool returns the summary row only. Read-only: it reads the embedded registry snapshot (optionally refreshed from the public registry when reachable), takes no parameters, performs no writes and needs no credentials. Repeated calls are identical until the snapshot is refreshed.

certification_specA

Return the dsh-plugin-certification specification document, version 1: the five graded dimensions, the grade scale from A to F, and the veto rule that can override a grade. Use this to interpret a grade you have already read - for example to learn why a record was vetoed, or what a dimension actually measures. Use list_certified or get_certification instead when you want a specific plugin's data rather than the rules behind it. Read-only: the document is compiled into the server, takes no parameters, performs no writes and needs no credentials. The same document is returned on every call.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a clearly distinct need: get_certification returns one plugin's record, list_certified enumerates the registry, and certification_spec returns the rules document. The descriptions explicitly cross-reference each other ('use list_certified instead when...'), leaving essentially no room for misselection.

Naming Consistency4/5

All names use snake_case, and two of three share the verb_ prefix pattern (get_certification, list_certified). Minor deviation: the noun forms differ (certification vs certified) and certification_spec drops the verb entirely, though it reads naturally as a document lookup.

Tool Count4/5

Three tools is on the lean side but proportionate for a read-only registry lookups service: single-record fetch, enumeration, and spec. Nothing feels padded or redundant, though it sits near the thin end of the 3-15 range.

Completeness4/5

The read-only surface covers the natural lifecycle: discover the registry, fetch a specific record with full evidence, and interpret the grading rules. Minor gap in that there is no filtering/search by grade or dimension, but agents can work around this by listing and reading records.

Maintenance

ActivityActive
ResponsivenessSyncing