Skip to main content
Glama

runx

by ai.runx

get_skill

Read-onlyIdempotent

Read one runx skill in full before running it: its manifest, the authority it asks for, its publisher and trust signals, and the exact command to install and run it through the runx CLI. Everything needed to decide whether to trust a skill arrives in this one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionNoExact version to read. Defaults to the latest published version.
skill_idYesSkill id in owner/name form, for example `ausca/browser-session`.

Schema Changelog

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

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Read' is consistent with these. No additional behavioral details (e.g., auth, rate limits, side effects) are provided, but the alignment with annotations keeps the score at a baseline level.

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 sentences, front-loaded with the verb and resource, and includes essential details without any fluff. It is efficient and well-structured.

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

Completeness5/5

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

The description fully covers what the tool does, what it returns (manifest, authority, publisher, trust signals, command), and its purpose (trust decision). Given the simplicity of the tool and absence of an output schema, no additional context is needed.

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 description coverage is 100% (both parameters have descriptions), so the baseline is 3. The description does not add extra semantics beyond the schema, so no higher score is warranted.

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 'Read' and the specific resource 'one runx skill', and distinguishes itself from search_skills by focusing on full details needed for trust decisions. It is unambiguous and concise.

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 mentions 'before running it', which indicates when to use the tool, but it does not explicitly reference the sibling tool search_skills as an alternative for finding skills. However, the purpose is clear enough that an agent would know to use this for inspection rather than discovery.

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

All runx toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: search_skills finds skills by criteria, while get_skill retrieves full details for a specific skill. There is zero overlap in functionality, making selection unambiguous.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: get_skill and search_skills. The verbs (get, search) are distinct and descriptive, and the noun (skill) is consistent, creating a predictable naming convention.

Tool Count3/5

With only two tools, the set is minimal and on the thin side of the typical 3-15 tool range. However, for a focused read-only discovery server, this count is defensible, though it does not offer the breadth usually expected from an MCP server.

Completeness5/5

The domain of discovering and inspecting runx skills is fully covered: search_skills provides the discovery mechanism, and get_skill provides the detailed inspection. There are no obvious missing operations for the stated purpose of evaluating and selecting skills.

Resources