Skip to main content
Glama
Sign In
n8n MCP Server

n8n MCP Server

by verzth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Test n8n Credential

n8n_test_credential

Test a credential's validity by sending a test request to the service. Provide the credential ID to verify it works before use.

Instructions

Test whether a credential is valid by making a test request to the service.

Args:

  • id (string): Credential ID to test

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": {
      "id": "<id>"
    },
    "name": "n8n_test_credential"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCredential ID to test

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

The description adds that the tool makes a 'test request to the service', which goes beyond the annotations. However, it does not disclose details like potential side effects, authentication requirements, or what occurs on success/failure beyond the basic notion of testing validity.

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 concise and front-loaded. The first sentence clearly states the purpose, and the subsequent parameter list is directly relevant. No unnecessary words or repetition.

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 simple one-parameter tool with no output schema, the description provides adequate but minimal context. It explains what the tool does but does not specify the return value or behavior on success/failure, which could be ambiguous. Additional details about expected outputs would improve completeness.

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?

The input schema already provides a full description for the 'id' parameter, and the description's mention of 'Credential ID to test' adds no new information beyond the schema. With 100% schema coverage, the baseline score applies.

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

Purpose5/5

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

The description clearly states the tool's purpose with a specific verb ('test') and resource ('credential'), and specifies the action ('making a test request to the service'). It distinguishes itself from sibling tools like get_credential by focusing on validity rather than retrieval.

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?

The description implies the tool should be used when you need to check credential validity, but it does not explicitly state when to use it versus alternatives, nor does it provide exclusion criteria. The intended use case is inferable but not clearly articulated.

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