Wawp MCP Server

set_config

Configure Wawp API credentials for the current session with instance ID, test number, and access token to enable authenticated API requests.

Instructions

Update your Wawp API credentials for the current session.

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

Input Schema

Name	Required	Description	Default
`instance_id`	No
`test_number`	No
`access_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.0Aug 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description is the sole source of behavioral information. It does disclose that the update applies 'for the current session', which is useful, but it omits potential side effects, persistence, validation behavior, or what happens if credentials are invalid. The poor coverage leaves significant uncertainty.

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 sentence that is front-loaded with the action and object. There is no wasted wording, and every word contributes meaning. It is appropriately concise for the information it conveys.

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?

With 3 parameters, no annotations, and no output schema, the description is severely under-specified. It tells the agent that credentials are updated but leaves the meaning of each parameter, the expected effects, and any return behavior unexplained. The description does not sufficiently support correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain any of the three parameters (instance_id, test_number, access_token). The unusual parameter 'test_number' is especially ambiguous. The description adds no meaning beyond the raw schema listing.

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 uses a specific verb 'Update' and identifies the resource as 'Wawp API credentials for the current session', which clearly distinguishes it from sibling tools focused on file sending, endpoint listing, and request execution. It is not a tautology, but it doesn't explicitly contrast with alternatives.

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. It does not mention situations requiring credential updates, prerequisites, or any exclusions. It is a standalone statement without usage context.

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

Deploy Server