Skip to main content
Glama
Sign In

aiqbench

by com.aiqbench
OverviewDiscussionsAdmin

Read a skill

get_skill

The SKILL.md and file list of one skill, to follow for the current task without installing it. What you read is exactly what aiqbench scanned. To read a skill find_skills suggested, pass its id: several skills share a name, and a name returns the best-trusted of them. Otherwise name it as the user wrote it: a skill name (case, spaces and a letter or two wrong are forgiven; correctedFrom then says what was asked), owner/repo/skill, the skill id or its aiqbench page link. An unknown name answers with didYouMean.

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": "get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description has to carry the whole burden, and it does most of it: it states what content comes back, that the content is identical to what was scanned, that nothing is installed, and how name collisions, fuzzy corrections and unknown names resolve. It says nothing about size limits or truncation for large skills, which is the main remaining gap.

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

Conciseness4/5

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

The description leads with the return value, then moves through how to identify the skill. Every clause adds information, but the middle instruction mixes routing guidance and collision behavior in one long sentence, which makes it slightly harder to parse.

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?

For a single-parameter read tool with no output schema, the description covers the return content, the no-install behavior, and the full space of input formats plus their resolution edge cases. Nothing an agent needs in order to call it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must explain the single 'name' parameter, and it does: skill name with case and spacing tolerated, owner/repo/skill, skill id, or page link. It also explains what happens when a name matches more than one skill (best-trusted wins) and what correctedFrom and didYouMean mean. This adds meaning the bare string schema cannot convey.

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 combines a specific verb and resource (return the SKILL.md and file list of one skill) with a scoping qualifier (read without installing). That makes it easy to tell apart from its sibling find_skills (which suggests skills) and install_command (which installs them).

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 tells the agent exactly how to act on a skill that find_skills suggested (pass its id) and sets the boundary against installing it. It does not explicitly say when this tool is the wrong choice, for example when nothing is known yet and find_skills should come first. This is clear, but not a full when/when-not treatment.

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

All aiqbench toolsInspect
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.

Resources