Clipform

Who Am I

clipform_whoami

Read-onlyIdempotent

Show the current identity: auth mode (api key, oauth, session, or anonymous), active workspace, and plan limits. Needs a signed-in Clipform account (an anonymous session is asked to sign in).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes	Describe the user's underlying goal in one sentence - not the tool you're calling.

Output Schema

TableJSON Schema

Name	Required	Description
`plan`	Yes	Plan limits for the active workspace
`links`	No	Workspace-level dashboard links - only present for a non-anonymous caller.
`notice`	No	Anonymous sessions only: the account is a temporary preview until claimed.
`auth_mode`	Yes	How this session is authenticated
`workspace`	Yes	Active workspace, or null when anonymous
`workspaces`	No	Workspaces the caller can target with workspace_id - present for session (dashboard) auth and the OAuth connector
`is_authenticated`	Yes	True for api_key, oauth, or session auth; false for anonymous
`default_workspace_id`	No	OAuth connector only: the workspace used when a tool call omits workspace_id

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 6, 2026
- addedOutput schema / properties / plan / properties / form_limit / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / plan / properties / form_limit / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / plan / properties / node_limit / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / plan / properties / node_limit / type
```
Removed value: -[
-  "number",
-  "null"
-]
```

Changed1 schema field changedOct 5, 2026

addedOutput schema / properties / notice

Added value: +{
+  "description": "Anonymous sessions only: the account is a temporary preview until claimed.",
+  "type": "string"
+}

Changed2 schema fields changedOct 3, 2026

addedOutput schema / properties / default_workspace_id

Added value: +{
+  "description": "OAuth connector only: the workspace used when a tool call omits workspace_id",
+  "type": "string"
+}

changedOutput schema / properties / workspaces / description

Previous value: -"All workspaces in the caller's company - only present for session (dashboard) auth"New value: +"Workspaces the caller can target with workspace_id - present for session (dashboard) auth and the OAuth connector"

Changed2 schema fields changedSep 4, 2026

changedOutput schema / properties / auth_mode / enum

Previous value: -[
-  "api_key",
-  "session",
-  "anonymous"
-]New value: +[
+  "api_key",
+  "oauth",
+  "session",
+  "anonymous"
+]

changedOutput schema / properties / is_authenticated / description

Previous value: -"True for api_key or session auth; false for anonymous"New value: +"True for api_key, oauth, or session auth; false for anonymous"

Changed3 schema fields changedAug 31, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence - not the tool you're calling.",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "context"
+]
```

addedOutput schema / properties / links

Added value: +{
+  "additionalProperties": false,
+  "description": "Workspace-level dashboard links - only present for a non-anonymous caller.",
+  "properties": {
+    "dashboard": {
+      "description": "Dashboard home for the active workspace.",
+      "type": "string"
+    },
+    "forms": {
+      "description": "Forms list for the active workspace.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "dashboard",
+    "forms"
+  ],
+  "type": "object"
+}

AddedAug 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds non-obvious behavior beyond that: the call fails/clarifies for anonymous sessions by asking them to sign in, which is real auth-flow context an agent needs.

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 sentences, zero waste: the first front-loads what is returned, the second states the auth prerequisite. Nothing needs to be re-read or inferred.

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

Completeness5/5

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

For a read-only identity tool with an output schema present, return-value documentation is unnecessary, and the description still goes further by naming the returned fields. The auth prerequisite closes the only remaining gap.

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?

There is a single 'context' parameter with 100% schema description coverage, so the schema already explains its meaning. The description adds nothing about how to phrase the context string, which is the correct baseline 3 when the schema does the work.

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?

States a specific verb ('show') and resource ('current identity'), then enumerates the exact payload: auth mode (with its four possible values), active workspace, and plan limits. No sibling tool in the list overlaps with an identity/whoami query, so the agent can route to it unambiguously.

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 conveys the use context (checking auth mode, workspace, and plan limits) and states the prerequisite that a signed-in account is required, with anonymous sessions being redirected to sign in. It stops short of explicit when-to-use/when-not phrasing or naming alternatives, but there is no competing sibling to disambiguate against.

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

All Clipform tools Inspect

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.