Skip to main content
Glama
Sign In

Clickwise Affiliate Network

by net.clickwise
OverviewDiscussionsAdmin

Get merchant credentials once

get_merchant_credentials

get_merchant_credentials: Returns a merchant API token only if the account has none yet. If one exists, it answers 409 and explains where the account holder can copy it. It never reveals an existing token.

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": {
      "application_id": "<application_id>",
      "access_secret": "<access_secret>"
    },
    "name": "get_merchant_credentials"
  }
}

Input Schema

NameRequiredDescriptionDefault
access_secretYes
application_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations it discloses the 409 response, that an existing token is never revealed, and that the token is only minted when none exists — valuable behavior for an agent to plan around. It does not explain what the token looks like on success, its lifetime, or what access_secret must be, so the mutation side effect implied by readOnlyHint=false is only indirectly conveyed.

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?

Three short sentences, front-loaded with the core rule, then the failure path, then the guarantee. Every sentence carries distinct information with no repetition of the title or name.

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 two-parameter tool with no output schema, the description covers the success/failure contract and the no-reveal guarantee well. The remaining gap is input semantics — what application_id and access_secret must be — which an agent needs in order to call it successfully.

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% for both required parameters, and the description never mentions application_id or access_secret at all. With two undocumented required inputs whose relationship (application plus its secret) matters for a credentials call, the description does not compensate for the schema gap.

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 states a specific verb and resource (returns a merchant API token) plus the decisive scope condition: only when the account has none yet. It also distinguishes the two outcomes (fresh token vs. 409 with a pointer to where the holder can copy the existing one), so an agent can tell exactly what this tool does and does not deliver.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It makes the calling condition explicit (first-time credential retrieval only) and effectively warns against repeated use by noting that an existing token is never returned and pointing to where the holder copies it instead. It stops short of naming a sibling tool or a prerequisite for the access_secret, so it is clear context rather than a full when/when-not map.

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

All Clickwise Affiliate Network toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources