Skip to main content
Glama

StoreTechScan — Ecommerce Tech Stack & ICP

Check StoreTechScan Credits & Quota

check_credits
Read-onlyIdempotent

Check your StoreTechScan credit balance and recent ledger transactions (when authenticated via Authorization: Bearer or X-API-Key HTTP header), or view the anonymous one-time 25-domain free trial policy and pay-as-you-go pack pricing. Costs 0 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the bar is lower; the description still adds real context by naming the auth headers (Bearer or X-API-Key), the anonymous one-time 25-domain trial, and the zero-credit cost. It could go further on what the ledger response contains, but the added auth and cost facts are substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence leads with the primary action (check balance and ledger) before the secondary anonymous branch. The parenthetical auth clause is dense but earns its place; only slight tightening is possible.

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 no-parameter, no-output-schema tool whose annotations already cover the safety profile, the description covers both the authenticated and anonymous paths, the auth mechanism, and the cost. The main residual gap is that the ledger response shape is only gestured at, which matters somewhat given there is no output schema.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter meaning to add. Nothing in the description conflicts with the empty schema.

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

Purpose4/5

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

States specific verbs and resources: credit balance, recent ledger transactions, free-trial policy, and pack pricing, with the authentication mode that selects each branch. It stops short of naming the sibling buy_credits, so the boundary between 'viewing pack pricing' here and 'purchasing' there is left implicit.

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 gives a clear condition (authenticated vs anonymous) that determines what the tool returns, but that is a behavioral branch rather than when-to-use guidance. It never says to use buy_credits when you actually want to purchase, nor when to call this versus inspect_domains or get_inspection_results.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources