Check the signed-in account's AI credit balance. Requires a ScanLabsAI API key in the MCP connection (Authorization: Bearer slai_...). Create one at https://scanlabsai.com/mcp.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the authentication requirement (ScanLabsAI API key) and that it operates on the signed-in account, which is useful behavioral context. It does not mention return format or rate limits, but for a simple read-only balance check this is acceptable.
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: the first states the purpose, the second covers authentication setup. It is front-loaded, concise, and every sentence serves a purpose.
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 zero-parameter, read-only tool with no output schema, the description covers the essential information: what it does, the account context, and the required auth. The expected return value (credit balance) is implied by the description. Missing explicit return format, but not critical for such a simple tool.
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 tool has zero parameters, so the baseline is 4. The description adds no parameter-specific details, but there are no parameters to describe, so this is appropriate.
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 the tool 'check the signed-in account's AI credit balance' with a specific verb and resource. This distinguishes it from sibling tools like buy_credits, which is about purchasing credits.
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 implies usage (checking balance before scanning), but it does not explicitly mention when to use this tool versus alternatives or provide any exclusion criteria. No reference is made to sibling tools like scan_agent or buy_credits.
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.