Asmit Dev Tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_password_breachA | Count how many times a password appeared in known data breaches. Privacy: only the first 5 characters of the SHA-1 hash are sent to Have I Been Pwned (k-anonymity). The password and the full hash are never sent, stored or logged. |
| password_strengthA | Score a password 0-5 and explain how to improve it. The password is scored locally and never sent anywhere. Score: one point each for length 8+, length 12+, mixed case, a digit, and a symbol. This is a strength hint, not a guarantee. |
| generate_passwordA | Generate a random password locally with the secrets module. The password is generated on the server machine and returned to the caller; it is never stored or sent anywhere else. Length is clamped to 8-64. |
| split_expenseB | Split an expense and simplify who owes whom. Equal split: the remainder poisha go to the first members, so the shares always add up exactly. Custom split: shares must sum exactly to the total, otherwise a validation error is returned. |
| settle_balancesA | Simplify any set of balances into the fewest payments. balances maps each person to what they are owed (+) or owe (-); the values must sum to zero. Money is handled in integer poisha. |
| convert_currencyB | Convert an amount between currencies using a free no-key rate API. Rates are indicative, from exchangerate-api.com, and are not financial advice. Rates are cached in memory for 5 minutes. |
| repo_healthB | Health summary of a PUBLIC GitHub repository, plus upgrades: top languages by bytes and open pull requests counted from the first 100 open PRs. If those extra calls fail, they are reported as null instead of failing the whole health check. |
| repo_compareC | Side-by-side health comparison of two public GitHub repositories. |
| github_user_summaryA | Public summary of a GitHub user: profile, repo count, total stars across their public repos, and most-used languages. Public data only, no token; private repos are invisible to the public API by design. |
| audit_tool_listA | Static security checklist for an MCP server's tool list. tools_json is a JSON list of {"name": ..., "description": ...}. Nothing is run and nothing connects to a live server. The result is a checklist score, not a safety certification. |
| check_url_statusA | Check whether a URL is reachable and what status it returns. SSRF guard (core.ssrf) runs before the request and again for every redirect target: only globally routable addresses may be fetched, at most 5 redirects. Only a HEAD request is made; nothing is downloaded fully and no form is submitted. "reachable: false" is a result, not an error: it means the check itself ran and the URL did not answer. |
| world_timeA | Current time in a given IANA timezone, plus UTC and Asia/Dhaka for comparison. timezone_name examples: Asia/Dhaka, Asia/Kolkata, Europe/London, America/New_York. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target clearly different resources: password checks vs. expense math vs. GitHub repo analysis vs. URL probing vs. time lookup. The only real overlap is split_expense, which also 'simplifies who owes whom', versus settle_balances which does the same simplification on a balance set; descriptions distinguish them but the boundary is soft.
Everything is snake_case, which is good, but the verb_noun convention is only partly followed: check_password_breach, generate_password, split_expense, convert_currency, check_url_status are verb-led, while password_strength, repo_health, repo_compare, github_user_summary, world_time are bare noun phrases. Readable, but not a predictable pattern an agent can extrapolate.
Twelve tools is a reasonable, well-scoped count with no obvious filler; each tool has a concrete job. The count is fine, though it is spread across many unrelated mini-domains rather than one coherent surface.
Each sub-domain is thin: expenses can be split and settled but there is no notion of groups, members, or persistence; currency offers only conversion with no rate lookup or supported-currency listing; GitHub covers health/compare/user but no repo search or issue/PR detail; time offers only current time with no conversion. Agents can work around these gaps, but they will hit dead ends for anything beyond a single call per domain.