Skip to main content
Glama

get_suites

Retrieve all test suites from a Qase project to organize and manage testing workflows efficiently.

Instructions

Get all test suites in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
searchNo
limitNo
offsetNo

Implementation Reference

  • Handler for the 'get_suites' tool call: parses arguments using GetSuitesSchema and delegates to the getSuites function.
    .with({ name: 'get_suites' }, ({ arguments: args }) => {
      const { code, search, limit, offset } = GetSuitesSchema.parse(args);
      return getSuites(code, search, limit, offset);
    })
  • Zod schema defining the input parameters for the get_suites tool: code (required), search, limit, offset (optional).
    export const GetSuitesSchema = z.object({
      code: z.string(),
      search: z.string().optional(),
      limit: z.number().optional(),
      offset: z.number().optional(),
    });
  • src/index.ts:220-224 (registration)
    Registration of the 'get_suites' tool in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'get_suites',
      description: 'Get all test suites in a project',
      inputSchema: zodToJsonSchema(GetSuitesSchema),
    },
  • Core getSuites function: pipes the client.suites.getSuites method to toResult utility for handling the API call and response.
    export const getSuites = pipe(
      client.suites.getSuites.bind(client.suites),
      toResult,
    );
Behavior2/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. It states it 'gets' data, implying a read operation, but doesn't cover aspects like pagination behavior (suggested by 'limit' and 'offset' parameters), error handling, authentication needs, or rate limits. This is a significant gap for a tool with multiple parameters.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

Given the complexity (4 parameters, 1 required), lack of annotations, and no output schema, the description is incomplete. It doesn't address parameter meanings, behavioral traits, or return values, leaving the agent with insufficient context to use the tool effectively beyond its basic purpose.

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

Parameters2/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 compensate but adds no parameter information. It doesn't explain what 'code', 'search', 'limit', or 'offset' mean, their formats, or how they affect the operation. With 4 parameters and no schema descriptions, this leaves key semantics undocumented.

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?

The description clearly states the action ('Get') and resource ('all test suites in a project'), making the purpose understandable. It doesn't explicitly differentiate from sibling tools like 'get_suite' (singular) or 'list_projects', but it's specific enough to convey its scope.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_suite' (singular) or 'list_projects'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rikuson/mcp-qase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server