TeamShared

memory_skill_get

Fetch a stored skill by name (and optionally version).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Skill name
`version`	No	Specific version (default: latest active)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "anyOf": [
-      {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedAug 18, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Fetch' implies a read-only operation with no side effects, but the description does not explicitly state this or mention error behavior (e.g., what happens if the skill does not exist). It adds only basic intent, nothing beyond the obvious read nature.

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 a single, front-loaded sentence that directly states the action and scope. Every word is useful, and there is no extraneous content. It is optimally concise for an effective tool description.

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 two parameters are fully documented in the schema and an output schema exists (so return format is not needed), the description is sufficient for an agent to call this tool correctly. It does not explain error handling or version semantics beyond what the schema provides, but for a simple fetch operation, this is adequate. A 4 reflects that it is complete with minor optional additions.

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

Parameters3/5

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

Schema coverage is 100%, with both 'name' and 'version' having descriptions. The description restates 'by name (and optionally version)' which is redundant with what the schema already provides. It adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate.

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 the verb 'Fetch' and the resource 'stored skill', and specifies the key parameter (name) and optional version. This distinguishes it from siblings like memory_skills_list (which lists all skills) and memory_skill_set (which writes skills). The purpose is unambiguous.

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 implies usage when a specific skill is needed by name, but does not explicitly mention alternatives or exclusions. The context is clear enough for an agent to infer that this tool is for fetching a single skill rather than listing or modifying, though explicit guidance would be better.

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

All TeamShared tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.