Skip to main content
Glama
mcp-server-vippsmobilepay

mcp-server-vippsmobilepay

Check Vipps MobilePay connection

vipps_check_connection
Read-onlyIdempotent

Verify Vipps MobilePay API credentials by requesting an access token and returning whether the connection works.

Instructions

Check that the keys work, by requesting an access token. Returns only whether the connection works.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds genuine value beyond them: it discloses that the call performs a live network auth request and that the response is limited to a pass/fail indicator, so an agent should not expect diagnostic detail from a failure.

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?

Two short sentences with zero filler: the mechanism is stated first, followed by the return-value limitation. Every clause carries information an agent would otherwise have to guess.

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 trivial, zero-parameter, non-destructive check with no output schema, the description covers the essentials: what it does and that the result is a simple boolean. The one remaining gap is failure semantics — whether invalid keys produce a false result or an error — which the agent must discover at call time.

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 no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The description correctly implies credentials come from server-side configuration rather than from the call itself.

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 names a specific action and resource: it validates the Vipps API keys by requesting an access token. The mechanism (token request) and the output scope (connection status only) make it clearly distinct from the sibling payment/charge/agreement tools, though no sibling is named explicitly.

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?

"Check that the keys work" implies the use case — verifying credentials before running real payment operations — but there is no explicit when-to-use statement, no guidance on how often to call it, and no note about what to do when it fails. Usage is inferable rather than stated.

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