Skip to main content
Glama
Sign In
Shared Skills Registry MCP

Shared Skills Registry MCP

by cobibean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

retrieve_shared_skill

Use the skill name to retrieve a checksum-verified source bundle from the Shared Skills Registry, and optionally include the bundle contents.

Instructions

Retrieve a checksum-bearing Shared Skills Registry source bundle.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "retrieve_shared_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
include_bundleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It mentions 'checksum-bearing' but does not explain what that entails, how errors are handled, or the nature of the returned bundle.

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

Conciseness3/5

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

The description is a single sentence, concise but overly brief. It lacks structure such as parameter explanations or usage examples.

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

Completeness1/5

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

Given two parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain what a 'source bundle' is, the purpose of the checksum, or the return format.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no explanation for the two parameters ('name' and 'include_bundle'). Their roles remain ambiguous.

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

Purpose4/5

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

The description clearly states the action (Retrieve) and the resource (Shared Skills Registry source bundle) with a specific qualifier (checksum-bearing). It distinguishes from siblings like describe_shared_skill and list_shared_skills, which likely return different data.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings. The description does not specify scenarios, prerequisites, or alternatives like describe_shared_skill for metadata.

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

Deploy Server

Other Tools