Skip to main content
Glama
Sign In

Tokenrip

by com.tokenrip
OverviewDiscussionsAdmin

Show my account

whoami
Read-onlyIdempotent

Get the current authenticated account profile. agentsUrl is the Agents page in your person's browser, where they add their next agent (a one-line code to paste into it) or create a key for a host that takes a pasted key; give them the link. Codes and keys are shown only to the person. agentsUrl is null when no person with a verified email is connected to your account; the next agent can then sign in with an email instead. key is this key's name and the workspaces it may use, or all.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idYes
keyYes
tagYes
aliasYes
emailYes
websiteYes
isPublicYes
metadataYes
agentsUrlYes
descriptionYes
registeredAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / key
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "access": {
+      "oneOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "mode": {
+              "const": "all",
+              "type": "string"
+            }
+          },
+          "required": [
+            "mode"
+          ],
+          "type": "object"
+        },
+        {
+          "additionalProperties": false,
+          "properties": {
+            "mode": {
+              "const": "limited",
+              "type": "string"
+            },
+            "workspaces": {
+              "items": {
+                "additionalProperties": false,
+                "properties": {
+                  "id": {
+                    "format": "uuid",
+                    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+                    "type": "string"
+                  },
+                  "level": {
+                    "enum": [
+                      "read",
+                      "write"
+                    ],
+                    "type": "string"
+                  },
+                  "name": {
+                    "type": "string"
+                  },
+                  "slug": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "id",
+                  "slug",
+                  "name",
+                  "level"
+                ],
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "required": [
+            "mode",
+            "workspaces"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "access"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "id",
-  "alias",
-  "tag",
-  "description",
-  "website",
-  "email",
-  "isPublic",
-  "metadata",
-  "registeredAt",
-  "agentsUrl"
-]New value: +[
+  "id",
+  "alias",
+  "tag",
+  "description",
+  "website",
+  "email",
+  "isPublic",
+  "metadata",
+  "registeredAt",
+  "agentsUrl",
+  "key"
+]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-structured context: that agentsUrl points at a page in the person's browser, that codes/keys are visible only to the person, and the null-condition when no verified-email person is attached. It does not say anything about cost or rate limits, but the added semantics clearly exceed the annotation set.

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

Conciseness3/5

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

The purpose is front-loaded in one clean sentence, but the middle clause ('where they add their next agent (a one-line code to paste into it) or create a key for a host that takes a pasted key') is tangled and takes effort to parse. The information earns its place, but the phrasing is denser and less ordered than it needs to be.

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?

With an output schema present, the description is not obligated to document return fields, yet it covers the two cases that actually matter operationally (agentsUrl present vs null, and what key represents). For a zero-parameter read tool with full annotation coverage, that is close to complete; only the murky wording of the agentsUrl explanation keeps it from being fully adequate.

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 no parameter surface to explain and the baseline of 4 applies. The description instead invests its words in output-field semantics, which is the relevant substitute for a parameterless tool.

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 opening sentence gives a specific verb and resource: 'Get the current authenticated account profile,' which distinguishes an identity lookup from the sibling account-style tools (folder_show, team_show, workspace_show). It stops short of explicitly contrasting with those siblings, but the word 'current authenticated' makes the scope unambiguous enough for an agent to select it.

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?

There is no explicit statement of when to call this versus the *_show siblings. The only directional guidance is about acting on the result ('give them the link'), which is usage of the output rather than guidance for selecting the tool. Usage is therefore implied rather than stated.

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

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