Skip to main content
Glama
Sign In
Asin MCP Server

Asin MCP Server

by asindotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Plan and remaining credits

get_account
Read-only

Check your plan, remaining monthly and pack credits, tracked product count, and monthly credit usage to monitor capacity and prevent tracking interruptions.

Instructions

Plan and remaining credits. Your plan, the credits left (monthly allowance and packs), how many products you track and the credits they use per month.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds only the shape of the payload, with no mention of auth requirements, whether the call is scoped to the authenticated account, or whether credits figures are live versus cached. With no output schema, that payload description is genuinely useful, but behavioral context remains thin.

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?

Two short sentences, front-loaded with the resource name and then the fields returned. The first sentence duplicates the title and could be dropped, which is the only real waste; nothing else is padded.

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 zero-parameter read tool with no output schema, the description covers the main return fields (plan, monthly allowance, packs, tracked-product count, monthly credit consumption) well enough for an agent to decide whether the response answers a quota question. Minor gaps remain around units, freshness and whether the counts are per-account or per-workspace.

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 there is nothing for the description to disambiguate beyond what the empty schema shows. Baseline 4 applies; the description does not mislead about any inputs.

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 expands the title into a list of data the tool surfaces (plan, credits left, monthly allowance and packs, tracked product count, credits consumed per month), so an agent can tell it returns account/billing state rather than product data. However there is no verb and the first sentence is a verbatim restatement of the title, so the actual action (fetch/read the account) is only implied.

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 guidance on when to call this instead of siblings such as list_products or get_offers, and no stated preconditions. The agent must infer that this is the entry point for quota/billing questions. The content list implies usage (check credits before tracking more products) but never says so.

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