Skip to main content
Glama

Kariaa Agents

Who am I

whoami
Read-only

Use when you need to know who is signed in and what they still need. The account behind the key, whether the basics a task needs are in (legal name, phone, location, occupation), and today's usage.

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
quotaNoToday's usage
missingNoBasics still missing
profileNoBasics on file
signed_inNoWhether a valid key was sent
ready_to_applyNoWhether the basics are complete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that identity comes from the API key rather than a parameter, but the rest of the second sentence restates return contents that the output schema already documents, and it says nothing about auth failure behavior.

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

Conciseness4/5

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

Two short sentences with the usage trigger front-loaded, and no filler. The second sentence is a comma-separated fragment that reads slightly loosely, but every element maps to real returned data.

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?

For a zero-parameter read tool with an output schema and annotations, most needs are already met by structured fields. The description covers identity, profile gaps, and usage, but omits what an agent should expect on an invalid or expired key, which is the main behavioral unknown left.

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 nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The implicit point that the account is identified by the key is a mild plus.

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 description names three concrete returns: the signed-in account, profile-completeness fields (legal name, phone, location, occupation), and today's usage. That clearly separates it from siblings like my_earnings or update_profile, though the core action is phrased as a question rather than a verb+resource.

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?

'Use when you need to know who is signed in and what they still need' gives an explicit triggering condition, including the onboarding-completeness angle an agent would use before applying to work. It does not name alternative tools or state when not to call it, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.