Skip to main content
Glama
Sign In

VulKill Security

by io.github.dytredline
OverviewDiscussionsAdmin

vulkill_credit_usage

Read-only

Güncel dönemin kredi kullanımını ve en son görev özetlerini getirir. view uyumluluk alanıdır; historical seçimi geçmiş dönem bakiyesi sorgulamaz. Anlık bakiye için vulkill_wallet_status kullanın. Kredi harcamaz.

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

Input Schema

NameRequiredDescriptionDefault
viewNoUyumluluk etiketi; varsayılan current. Her iki değer güncel dönem bakiyesini ve son görevleri getirir.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / view / description
      Added value: +"Uyumluluk etiketi; varsayılan current. Her iki değer güncel dönem bakiyesini ve son görevleri getirir."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower. The description still adds genuinely useful context beyond them: the tool does not consume credits ('Kredi harcamaz'), which matters in a family of credit-related tools, plus the counterintuitive behavior that the view flag is only a compatibility label.

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

Conciseness5/5

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

Four short sentences, front-loaded with what is returned, then the caveat, then the alternative, then the cost note. No filler and nothing repeated unnecessarily.

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 single-optional-parameter read-only tool with annotations covering safety and no output schema, the description covers return content at a summary level and flags cost and scoping quirks. Only the overlap with vulkill_check_credits is left unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema's own description of view already explains that both enum values return current-period data. The description restates that same point rather than adding new meaning, so the baseline 3 is appropriate.

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?

The description names a specific verb and two concrete resources: current-period credit usage and latest task summaries. It distinguishes itself from vulkill_wallet_status by scope, though it leaves the similarly named sibling vulkill_check_credits unaddressed, so an agent must still guess between those two.

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

Usage Guidelines4/5

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

It gives explicit routing guidance ('Anlık bakiye için vulkill_wallet_status kullanın') and a when-not caveat that historical does not query past-period balances. What is missing is a comparison against vulkill_check_credits, which appears to overlap heavily with this tool.

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

All VulKill Security toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources