Skip to main content
Glama
Sign In

knos

by io.github.drexthealpha
OverviewDiscussionsAdmin

A session for the money tools

knos_sign_in
Destructive

Returns a guest session token that the tools moving devnet test money accept; ask your human first.

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": {
      "label": "<label>"
    },
    "name": "knos_sign_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYesa note on who opened it; never shown (the session shows as Guest and 4 characters of its id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / label / description
      Previous value: -"who your human is (a display label)"New value: +"a note on who opened it; never shown (the session shows as Guest and 4 characters of its id)"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description is not required to carry the full safety burden. The description adds the devnet-only scope and that the resulting session appears as 'Guest' with 4 id characters, but it never explains why this is destructive or whether creating a new session invalidates an existing one.

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?

A single sentence that front-loads the return value, then the consumer, then the human-approval caveat. No filler or redundant restatement of the title.

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?

There is no output schema, so the description correctly does mention that a token is returned. However, for a destructive, non-idempotent session-creation tool it omits token lifetime/expiry, whether repeated calls mint additional sessions, and what 'ask your human first' practically requires.

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 already explains that label is a private note identifying who opened the session. The description adds nothing about the parameter, which is acceptable given full coverage but leaves no extra value.

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?

States a specific verb and resource: returns a guest session token accepted by the devnet test-money tools. It distinguishes itself from the financial siblings by framing the token as the prerequisite for those tools, though it never names them individually.

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

Usage Guidelines3/5

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

Implies when to use it (before calling tools that move devnet test money) and adds a prerequisite, 'ask your human first.' It does not say what to do if a session already exists or whether sessions can be reused, so the guidance is implied rather than explicit.

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

All knos 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