Skip to main content
Glama

skillporter_matrix

Read-only

Return the compatibility matrix of all 19 supported AI agent harnesses. Use it to check which harnesses a skill can target before auditing coverage in a workspace.

Instructions

[READ] Return the compatibility matrix of all 19 supported AI agent harnesses.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the '[READ]' tag restates that rather than adding to it. The description does add the useful scope fact that the result covers all 19 harnesses with no filtering, but it says nothing about return shape, ordering, or whether the matrix is static or reflects the current environment.

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?

A single front-loaded sentence with no wasted clauses, and the key scope detail (all 19 harnesses) arrives immediately. The '[READ]' prefix is mild redundancy against the readOnlyHint annotation, which keeps it from being maximally tight.

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?

For a zero-parameter, no-output-schema lookup, the description conveys what the call returns (a compatibility matrix across all harnesses) and needs no more to be invoked correctly. A brief note on what a matrix entry contains would make it fully self-sufficient.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies the call is unfiltered and global rather than parameterized.

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?

States a concrete verb ('Return') and a concrete resource ('compatibility matrix of all 19 supported AI agent harnesses'), which is specific enough to distinguish it from inspect/detect/status siblings that describe a single harness or project state. It stops short of naming a sibling or explicitly contrasting scope, so it is clear but not maximally differentiated.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for checking which harnesses are compatible, but there is no explicit 'use this when…' or 'use X instead for…' guidance. No prerequisites or exclusions are stated, and the '[READ]' prefix gives only a weak hint about invoking it in a non-mutating phase.

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