Skip to main content
Glama
Sign In
shoonya-mcp

shoonya-mcp

by benatcmathew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

login

Authenticate to Shoonya by decrypting local encrypted credentials with your master password. AI never accesses the password.

Instructions

Securely login to Shoonya using encrypted credentials from the local vault. The AI never sees passwords. Requires the master_password to decrypt the vault.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "master_password": "<master_password>"
    },
    "name": "login"
  }
}

Input Schema

NameRequiredDescriptionDefault
master_passwordYesMaster password to decrypt the credential vault

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses secure credential handling and that the AI never sees passwords, but it omits details on session management, error behavior, and post-login state.

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?

Two concise sentences with the purpose front-loaded. Every word adds value, no redundancy.

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

Completeness2/5

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

No output schema is provided, and the description does not specify return values (e.g., session token) or failure modes (e.g., invalid password). This is a significant gap for an authentication tool.

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%, so the description adds little beyond the schema. It mentions the vault concept but provides no additional format or constraints for the master_password.

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

Purpose5/5

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

The description clearly states the action (login) and the target system (Shoonya) using encrypted credentials. It differentiates from sibling order tools by being the authentication step.

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?

The description implies usage when authentication to Shoonya is needed, but does not explicitly state when not to use it or mention alternatives. However, the context of sibling tools makes the usage context clear.

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