Skip to main content
Glama
Sign In
k11 API Functional QA

k11 API Functional QA

Official
by K11-Software-Solutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Call API

call_api

Send one API request to explore an endpoint and check its response while writing tests; write guardrails, masked secrets, and schema validation apply.

Instructions

Make one request (e.g. call='GET /orders/{id}', path_params={'id': '1001'}) to explore an API while writing tests. Same guardrails as flows: writes only where allowed, secrets masked, schema checked when a spec is set.

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": {
      "call": "<call>"
    },
    "name": "call_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
authNo
bodyNo
callYes
queryNo
headersNo
environmentNo
path_paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that writes are only permitted where allowed, secrets are masked, and responses are schema-checked when a spec exists. It omits auth/permission behavior and what a response or failure looks like, so it is not complete.

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?

Two sentences, front-loaded with the request-shape example, and the guardrail note is compact. Little waste, though the parenthetical example is dense with syntax that could be separated for readability.

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

Completeness3/5

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

For a 7-parameter tool with no annotations and no output schema, the description covers safety guardrails but says nothing about return values, error/validation feedback, or how auth and environment interact. It is adequate to attempt a call but leaves real gaps for correct invocation.

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 coverage is 0% across 7 parameters, and the description only clarifies the `call` string format (method + path) and gives a `path_params` example. The remaining parameters — auth, body, query, headers, environment — are undocumented in both the schema and the description.

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 states a specific verb and resource — make one request to explore an API while writing tests — and gives a concrete call shape ('GET /orders/{id}'). It does not explicitly differentiate itself from siblings like draft_flow or run_flows, so it falls short of a 5.

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?

'While writing tests' implies the context of use, but there is no explicit when-not-to-use guidance and no named alternative to pick instead. The 'Same guardrails as flows' clause references flows generally without telling the agent which sibling tool to choose in a given situation.

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

Deploy Server

Other Tools