Skip to main content
Glama
qa-toolkit-mcp

qa-toolkit-mcp

by darizae

qa_capabilities

Lists available QA operations and reports evidence status to help you confirm supported checks and evidence limits before planning tests.

Instructions

Describe available operations and evidence status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does imply this is a non-mutating introspection call. However, it says nothing about what 'evidence status' contains, whether the response is a static list or reflects live state, or how large the output is, leaving the agent to discover the shape by calling it.

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 filler, which is the right scale for a zero-parameter tool. The terseness is efficient rather than padded, though the vague phrasing of 'evidence status' costs it the top mark.

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?

The tool is simple: no parameters, no nested objects, no output schema. Even so, the description stops short of saying what the agent gets back or why 'evidence status' matters, so the agent knows the call is safe but not what it will learn. The score is capped slightly by that output-side gap.

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 argument object is empty, so there are no parameters whose semantics need explaining; the baseline of 4 applies. The description cannot add parameter meaning beyond what is already absent, and nothing it says conflicts with the zero-argument schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'describe' plus 'available operations and evidence status' signals an introspection/capabilities tool, but both nouns are vague: neither 'operations' nor 'evidence status' is grounded in a concrete resource. It also overlaps with the sibling qa_discover_api_surface, and the description does nothing to separate the two.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of the situation that selects this tool over qa_discover_api_surface, qa_audit_case_references, or qa_compile_indexed_cases. With zero parameters an agent could call it cheaply, but it must infer the trigger condition entirely.

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