Bernstein - Multi-agent orchestration

load_skill

List available skills or load a named skill's body, reference, or script file contents as text to review before use.

Instructions

List available skills when name is omitted, or load a named skill body, reference, or script file contents. Returns file contents as text; executes nothing. Host effects: reads files.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Skill to load. Omit to return the compact skill index.
`script`	No
`reference`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

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

Changed2 schema fields changedv3.15.0Aug 14, 2026

changedInput schema / description

Previous value: -"List available skills when name is omitted, or load a named skill body, reference, or script."New value: +"List available skills when name is omitted, or load a named skill body, reference, or script file contents. Returns file contents as text; executes nothing. Host effects: reads files."

addedInput schema / timeoutSeconds
```
Added value: +30
```

Changed23 schema fields changedv3.11.0Jul 28, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / dependencies
```
Added value: +{
+  "reference": [
+    "name"
+  ],
+  "script": [
+    "name"
+  ]
+}
```
- addedInput schema / description
```
Added value: +"List available skills when name is omitted, or load a named skill body, reference, or script."
```
- addedInput schema / properties / name / description
```
Added value: +"Skill to load. Omit to return the compact skill index."
```
- addedInput schema / properties / name / maxLength
```
Added value: +128
```
- addedInput schema / properties / name / minLength
```
Added value: +1
```
- addedInput schema / properties / name / pattern
```
Added value: +"^[A-Za-z0-9_.-]+$"
```
- removedInput schema / properties / name / title
```
Removed value: -"Name"
```
- removedInput schema / properties / reference / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / reference / default
```
Removed value: -null
```
- addedInput schema / properties / reference / maxLength
```
Added value: +256
```
- addedInput schema / properties / reference / pattern
```
Added value: +"^[A-Za-z0-9_./-]+$"
```
- removedInput schema / properties / reference / title
```
Removed value: -"Reference"
```
- addedInput schema / properties / reference / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedInput schema / properties / script / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / script / default
```
Removed value: -null
```
- addedInput schema / properties / script / maxLength
```
Added value: +256
```
- addedInput schema / properties / script / pattern
```
Added value: +"^[A-Za-z0-9_./-]+$"
```
- removedInput schema / properties / script / title
```
Removed value: -"Script"
```
- addedInput schema / properties / script / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedInput schema / required
```
Removed value: -[
-  "name"
-]
```
- changedInput schema / title
```
Previous value: -"load_skillArguments"New value: +"load_skill"
```
Addedv2.7.0May 25, 2026
Removedv2.6.0May 22, 2026
Addedv2.2.0May 18, 2026
Removedv2.1.0May 18, 2026
Addedv1.10.8May 13, 2026
Removedv1.10.7May 11, 2026
First observedv0.1.0Apr 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations available, the description carries full burden. It discloses that it returns file contents as text, executes nothing, and reads files. This clearly signals a read-only, safe operation. It could further mention error behavior (e.g., not found), but the provided info is solid.

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?

Two sentences, tightly packed with meaningful content: behavior, return type, safety, and host effect. Every word earns its place; no filler or 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?

Given the simple tool structure, an output schema exists, and the description covers core behavior and safety, it is mostly complete. It could be improved by explaining how missing files are handled, but that is a minor gap. Overall, it supplies enough for an agent to use the tool correctly.

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?

Schema description coverage is only 33% (only name has a description), so the description must compensate. It adds meaning by mentioning 'skill body, reference, or script file contents', mapping to the three possible loads. However, it does not explain the exact format or relationship of script/reference parameters beyond what dependencies imply.

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 clearly states two distinct behaviors: listing skills when name is omitted and loading skill body/reference/script contents when name is provided. The verb 'list' and 'load' are specific and the resource is well-defined, distinguishing it from the bernstein_* siblings.

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 description explicitly says 'when name is omitted' versus when a name is provided, giving clear context for both usage modes. It also notes 'executes nothing', implying it is for inspection, not execution, but it does not name alternative tools for execution, so it misses explicit when-not-to-use guidance.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/sipyourdrink-ltd/bernstein'

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