whoamiWhat this app may do for the person: the three spheres and how far you may go in each, the scopes they approved and not (what each allows, which actions need confirm: true), their households and groups by name. Call it when they ask what you can do, or when a tool you expect is missing.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / (root)Previous value: -{
- "$schema": "http://json-schema.org/draft-07/schema#",
- "additionalProperties": false,
- "properties": {
- "client": {
- "additionalProperties": false,
- "properties": {
- "autoSend": {
- "type": "boolean"
- },
- "name": {
- "type": "string"
- }
- },
- "required": [
- "name",
- "autoSend"
- ],
- "type": "object"
- },
- "groups": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "conversationId": {
- "type": "string"
- },
- "name": {
- "type": "string"
- }
- },
- "required": [
- "name",
- "conversationId"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "households": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "name": {
- "type": "string"
- },
- "role": {
- "type": "string"
- }
- },
- "required": [
- "name",
- "role"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "manageUrl": {
- "type": "string"
- },
- "notGranted": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "id": {
- "type": "string"
- },
- "title": {
- "type": "string"
- }
- },
- "required": [
- "id",
- "title"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "note": {
- "type": "string"
- },
- "person": {
- "additionalProperties": false,
- "properties": {
- "handle": {
- "type": [
- "string",
- "null"
- ]
- },
- "name": {
- "type": "string"
- }
- },
- "required": [
- "name",
- "handle"
- ],
- "type": "object"
- },
- "places": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "administer": {
- "type": "boolean"
- },
- "key": {
- "type": "string"
- },
- "publishRoutinePosts": {
- "type": "boolean"
- }
- },
- "required": [
- "key",
- "administer",
- "publishRoutinePosts"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "policy": {
- "additionalProperties": false,
- "properties": {
- "anon": {
- "type": "string"
- },
- "dailyAgentCap": {
- "type": "number"
- },
- "friends": {
- "type": "string"
- },
- "groups": {
- "type": "string"
- },
- "knocks": {
- "type": "string"
- },
- "places": {
- "type": "string"
- },
- "professional": {
- "type": "string"
- },
- "search": {
- "type": "string"
- }
- },
- "required": [
- "friends",
- "anon",
- "knocks",
- "search",
- "groups",
- "professional",
- "places",
- "dailyAgentCap"
- ],
- "type": "object"
- },
- "proRules": {
- "type": "string"
- },
- "scopes": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "id": {
- "type": "string"
- },
- "needsConfirm": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "reads": {
- "type": "string"
- },
- "title": {
- "type": "string"
- },
- "writes": {
- "type": "string"
- }
- },
- "required": [
- "id",
- "title",
- "reads",
- "writes",
- "needsConfirm"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "spheres": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "id": {
- "type": "string"
- },
- "level": {
- "type": "string"
- },
- "means": {
- "type": "string"
- }
- },
- "required": [
- "id",
- "level",
- "means"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "person",
- "client",
- "spheres",
- "proRules",
- "places",
- "scopes",
- "notGranted",
- "policy",
- "households",
- "groups",
- "manageUrl",
- "note"
- ],
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral detail beyond annotations: it returns approved and unapproved scopes, what each scope allows, which actions require confirm: true, and household/group names.
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?
It is compact, but the first sentence is a dense fragment and terms like 'three spheres' and 'how far you may go' are vague rather than operational. The usage guidance is front-loaded in the second sentence, but the return content could be expressed with clearer structure.
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?
With no parameters and no output schema, the description needs to explain what comes back, and it does enumerate scopes, permissions, confirmation requirements, households, and groups. It remains incomplete because 'three spheres' is undefined and no exact return shape is given.
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?
This tool has zero parameters, so there are no parameter semantics to explain. The baseline score of 4 applies because the schema is empty and complete.
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 clearly says it reports what the app may do for the person, including scopes, permissions, households, and groups. It is specific enough to distinguish capability introspection from ordinary profile or identity reads, though the name/title 'whoami' suggests identity and the phrase 'three spheres' is left undefined.
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?
It gives explicit triggering contexts: when the person asks what the assistant can do, or when an expected tool is missing. It does not mention when not to use it or name alternatives such as more_tools, use_tool, or list_identities.
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.