Get a secure Stripe checkout link to buy an AI credit pack for the signed-in account. Requires a ScanLabsAI API key in the MCP connection. Credits are added automatically once payment completes. Packs: starter (5), pro (15), agency (50).
| Name | Required | Description | Default |
|---|---|---|---|
| pack | No | Pack id: starter, pro, or agency. Defaults to pro. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description takes on the burden of disclosing side effects. It explicitly states 'Credits are added automatically once payment completes', indicating a mutation, and notes the API key requirement. This is transparent enough, though it doesn't detail failure modes or full payment flow, which are less critical in this context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded, and every sentence carries meaningful information: what it does, prerequisites, side effects, and pack options. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one optional parameter and no output schema, the description covers the essential aspects: purpose, prerequisites, behavioral outcome, and pack definitions. It would benefit from a note about the return value (the checkout link), but that is evident from the first sentence.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema describes the 'pack' parameter only as 'Pack id: starter, pro, or agency'. The description adds crucial semantics by enumerating the packs and their credit amounts ('starter (5), pro (15), agency (50)'), going beyond the schema. Since schema coverage is already 100%, this extra context earns a 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action: 'Get a secure Stripe checkout link to buy an AI credit pack'. This distinguishes the tool from siblings like check_credits and get_pricing. It also lists concrete pack options with credit amounts, further clarifying the tool's scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context for when to use the tool (when purchasing credits) and notes a prerequisite ('Requires a ScanLabsAI API key in the MCP connection'). However, it doesn't explicitly mention alternatives or when not to use this tool, though siblings make the use case obvious.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are mostly distinct: billing, scanning websites, scanning AI agents, CVE lookup, and remediation guidance all serve clear separate purposes. The main overlap is between compliance_report and scan_website, both assessing sites but from different angles; however descriptions clarify the distinction.
Most tools follow verb_noun pattern (buy_credits, check_credits, get_fix_guidance, get_pricing, lookup_cves, scan_agent, scan_website). 'compliance_report' is a noun phrase rather than a verb action, slight deviation but not confusing.
8 tools is well-scoped for a security scanning service. Each tool covers a necessary function: billing, pricing, scanning, compliance, CVE lookup, and remediation guidance, without unnecessary bloat.
The surface provides core lifecycle coverage for the domain: scanning (web and AI agent), compliance assessment, vulnerability intelligence, fix guidance, and credit management. Minor gaps exist like scan history or saved reports, but the tools handle real-time needs without dead ends.