Skip to main content
Glama

whoami

Verify the flomo connection by displaying the signed-in account plus total note and tag counts, and return an error if no flomo login is active.

Instructions

验证 flomo 连接:显示当前登录账号、笔记与标签总数。未登录时报错,需先在 flomo 应用中登录

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
proYes
accountYes账号显示名(无名称时为脱敏邮箱)
tag_countYes
memo_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does so for the key behaviors: it reports account and aggregate counts, it is a read/verification operation, and it fails with an error when unauthenticated. What it omits — timing, whether failures include an error code, or whether counts are cached — is minor for a small diagnostic call.

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?

One sentence plus one short clause: the function is front-loaded, then the failure precondition. Nothing is repeated, and every clause (what is shown, what happens when logged out, what to do first) carries information an agent needs.

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?

An output schema exists, so return-value structure is already covered, and the description still names the payload fields an agent should expect. For a parameterless verification tool with stated precondition and failure mode, no material gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 about inputs. Per the zero-parameter baseline this is fully adequate, and the description correctly implies the call is argument-free.

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?

The description names a specific action and resource: verifying the flomo connection and reporting the logged-in account plus note and tag totals. It is unmistakably distinct from every listed sibling (all memo/tag CRUD or sync operations), so an agent can route to it without inspecting the schema.

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?

It states the operative precondition that the caller must already be logged in via the flomo app and that the call errors otherwise, which is the essential guidance for a diagnostic tool. It does not spell out an explicit 'use this before X' workflow, but no sibling performs connection validation, so there is no real alternative to disambiguate against.

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