Skip to main content
Glama
Sign In
smart-token-guard

smart-token-guard

by nwjnjjj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

stg_pricing

Check SmartTokenGuard plan prices and checkout links to budget AI video quality checks; no license required.

Instructions

Plans, prices and checkout links for SmartTokenGuard. No license needed.

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": "stg_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one useful trait - no license is required to call it - but says nothing about side effects, whether it is read-only, or whether it implies any checkout/authorization action, which is a notable gap given the checkout-links wording.

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?

It is a single terse sentence, front-loaded with the useful content and free of filler. The phrasing is slightly telegraphic ('Plans, prices and checkout links') but nothing is wasted.

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

Completeness3/5

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

With an output schema present, return values need not be described, and with zero parameters the schema burden is nil. What remains is an adequate but thin definition: the auth note is covered, yet the nature of the operation and its role among the stg_* siblings is left implicit.

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 of 4 applies; the schema has nothing for the description to elaborate on. No parameter-level meaning is missing.

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

Purpose3/5

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

The description lists what the tool surfaces (plans, prices, checkout links) which gives a reasonable sense of the resource, but offers no verb and never states the operation, so the agent must infer that this is a lookup/model-retrieval tool. No sibling overlap is apparent, but there is no explicit differentiation either.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when another sibling (e.g. stg_account or stg_spend_report) would be the better choice, and no task context. The only usable hint is 'No license needed', which is a precondition rather than usage direction.

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

Deploy Server

Other Tools