whoamiWho this token is: its label, scopes, the revnu account it belongs to, and the rate limits it is held to. Needs no scope. Its scopes say which tools this token can use.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| me | Yes | Connected business, token permissions and rate limits. |
Changes observed during successful MCP inspections.
Output schema / properties / me / properties / account / descriptionAdded value: +"The business this connection operates on."Output schema / properties / me / properties / account / properties / id / descriptionAdded value: +"Revnu business account ID that owns this token."Output schema / properties / me / properties / account / properties / name / descriptionAdded value: +"Business display name, or null before one is known."Output schema / properties / me / properties / createdAt / descriptionPrevious value: -"Unix epoch milliseconds."New value: +"When this token was issued, as Unix epoch milliseconds."Output schema / properties / me / properties / inSetup / descriptionAdded value: +"True while onboarding is incomplete. Call setup_status for the exact next step."Output schema / properties / me / properties / label / descriptionAdded value: +"Human-readable name assigned to this token or connected app."Output schema / properties / me / properties / lastUsedAt / descriptionPrevious value: -"Unix epoch milliseconds."New value: +"Most recently recorded use as Unix epoch milliseconds, updated at minute granularity; null before any recorded use."Output schema / properties / me / properties / limits / descriptionAdded value: +"Configured rate-limit capacities, not remaining request balances. An HTTP 429 response supplies Retry-After."Output schema / properties / me / properties / limits / properties / account / descriptionAdded value: +"Shared request allowance across this business's tokens."Output schema / properties / me / properties / limits / properties / account / properties / burst / descriptionAdded value: +"Maximum requests accepted in a burst."Output schema / properties / me / properties / limits / properties / account / properties / perMinute / descriptionAdded value: +"Configured request rate per minute."Output schema / properties / me / properties / limits / properties / messages / descriptionAdded value: +"Agent-message allowance for this token."Output schema / properties / me / properties / limits / properties / messages / properties / burst / descriptionAdded value: +"Maximum requests accepted in a burst."Output schema / properties / me / properties / limits / properties / messages / properties / perMinute / descriptionAdded value: +"Configured request rate per minute."Output schema / properties / me / properties / limits / properties / reads / descriptionAdded value: +"Read-request allowance for this token."Output schema / properties / me / properties / limits / properties / reads / properties / burst / descriptionAdded value: +"Maximum requests accepted in a burst."Output schema / properties / me / properties / limits / properties / reads / properties / perMinute / descriptionAdded value: +"Configured request rate per minute."Output schema / properties / me / properties / limits / properties / writes / descriptionAdded value: +"Write-request allowance for this token."Output schema / properties / me / properties / limits / properties / writes / properties / burst / descriptionAdded value: +"Maximum requests accepted in a burst."Output schema / properties / me / properties / limits / properties / writes / properties / perMinute / descriptionAdded value: +"Configured request rate per minute."Output schema / properties / me / properties / scopes / descriptionAdded value: +"Permissions granted to this token. A missing scope does not mean the business lacks that capability."Output schema / properties / me / properties / tokenId / descriptionAdded value: +"Identifier of this access token, not its secret bearer value."Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": true,
+ "properties": {
+ "me": {
+ "additionalProperties": false,
+ "description": "Connected business, token permissions and rate limits.",
+ "properties": {
+ "account": {
+ "additionalProperties": false,
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "name"
+ ],
+ "type": "object"
+ },
+ "createdAt": {
+ "description": "Unix epoch milliseconds.",
+ "type": "number"
+ },
+ "inSetup": {
+ "type": "boolean"
+ },
+ "label": {
+ "type": "string"
+ },
+ "lastUsedAt": {
+ "description": "Unix epoch milliseconds.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "limits": {
+ "additionalProperties": false,
+ "properties": {
+ "account": {
+ "additionalProperties": false,
+ "properties": {
+ "burst": {
+ "type": "number"
+ },
+ "perMinute": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "perMinute",
+ "burst"
+ ],
+ "type": "object"
+ },
+ "messages": {
+ "additionalProperties": false,
+ "properties": {
+ "burst": {
+ "type": "number"
+ },
+ "perMinute": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "perMinute",
+ "burst"
+ ],
+ "type": "object"
+ },
+ "reads": {
+ "additionalProperties": false,
+ "properties": {
+ "burst": {
+ "type": "number"
+ },
+ "perMinute": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "perMinute",
+ "burst"
+ ],
+ "type": "object"
+ },
+ "writes": {
+ "additionalProperties": false,
+ "properties": {
+ "burst": {
+ "type": "number"
+ },
+ "perMinute": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "perMinute",
+ "burst"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "reads",
+ "writes",
+ "messages",
+ "account"
+ ],
+ "type": "object"
+ },
+ "scopes": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "tokenId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "tokenId",
+ "label",
+ "scopes",
+ "createdAt",
+ "lastUsedAt",
+ "account",
+ "limits"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "me"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered; the description adds genuinely non-redundant behavior by stating that the call requires no scope and that the returned scopes govern which other tools are usable. That auth-and-capability context goes beyond the annotations and is directly actionable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the identity payload and followed by the two constraints that matter (no scope needed; scopes gate other tools). The final sentence restates 'scopes' already listed in sentence one, a small redundancy, and 'revnu' reads as a typo, but overall the text is tight.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read tool with an output schema and rich annotations, the description covers the essentials: what is returned, that no scope is required, and how the result informs later calls. The one gap is the absence of any relationship to agent_status, which the agent must guess at.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4; the description correctly says nothing about arguments and instead spends its words on what the call returns. No parameter-level meaning is missing because there are no parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description enumerates exactly what is returned (token label, scopes, owning account, rate limits), which makes the tool unmistakable against the list/get siblings such as leads_list or workflow_runs. It is a noun phrase rather than a verb+resource, and it never names a sibling, but the resource (the calling token itself) is unique among the sibling set.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Needs no scope' and 'its scopes say which tools this token can use' imply the use case (checking credentials and capability before calling other tools), but the description never states when to call this versus agent_status, which is a plausibly overlapping sibling. Usage must be inferred rather than read.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.