Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Refresh Business Name Payment Link

refresh_business_name_payment_link
Idempotent

Reissues an ASIC card-payment link for a cancelled business-name application and returns the payment URL, recovering the same requestId after link expiry or card decline.

Instructions

Re-issue the ASIC card-payment link for a business-name application whose status is "cancelled" (link expired, cancelled or card declined). Recovers the SAME application under the same requestId; fails if already paid/registered. Returns response.transactionPaymentUrl.

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": {
      "request_id": "<request_id>"
    },
    "name": "refresh_business_name_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: it recovers the existing application rather than creating a new one, discloses the key failure mode (already paid/registered), and identifies the return field transactionPaymentUrl. It says nothing about authorization requirements or how the old link is invalidated, which is the remaining gap for a non-read-only, open-world tool.

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?

Tightly front-loaded: the action and triggering status come first, then the identity-preservation guarantee, then the failure mode, then the return path. No filler sentences; every clause carries decision-relevant information.

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

Completeness5/5

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

For a single-parameter tool with full annotations and an output schema, the description covers the precondition, the recovery semantics, the failure case, and the response field. Nothing an agent needs in order to decide to call it or to interpret failure is missing.

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 schema declares only an untyped integer request_id at 0% description coverage, so the description must carry the load, and it does: it establishes that request_id is the identifier of the original (cancelled) application being re-issued. It does not say where that requestId comes from or how to obtain it.

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?

States a specific verb and resource ('Re-issue the ASIC card-payment link') plus a narrow scope: business-name applications whose status is cancelled. It also differentiates itself from a fresh lodgement by saying it 'Recovers the SAME application under the same requestId', so an agent can tell it apart from lodge_business_name_registration without opening either schema.

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?

Gives an explicit trigger condition (status 'cancelled', with the causes spelled out: link expired, cancelled, or card declined) and an explicit exclusion ('fails if already paid/registered'). It stops short of naming the alternative tool to call when the application is already paid or registered, leaving that routing to inference.

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