Skip to main content
Glama

Read connected account

account
Read-onlyIdempotent

Read the Tofu account this connection acts for. id is the account’s opaque id: the same across refreshes and reconnections, and never given to another account. email is the address Tofu holds for it, and name its display name; each is absent when Tofu holds none. It takes no arguments, changes nothing and says nothing about the account’s apps.

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": "account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idYes
nameNo
emailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower, yet the description adds real substance: `id` is stable across refreshes and reconnections and never reassigned to another account, and `email`/`name` are absent when Tofu holds none. It also explicitly disclaims side effects and scope, which is exactly the context annotations cannot convey.

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?

Three tight sentences, front-loaded with the purpose, then field semantics, then the negative scope. Every clause carries information: stability guarantees, nullability rules, and the apps exclusion. No filler.

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 zero-argument, read-only tool with an output schema and full annotation coverage, the description supplies the remaining useful context: identity stability, when fields may be missing, and what the tool deliberately does not cover. Nothing needed to call or interpret it is missing.

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?

There are zero parameters, so the baseline is 4; the description goes further by documenting the semantics of the returned fields (opaque, stable, unique `id`; conditionally-absent `email` and `name`), which aids interpretation even though an output schema exists.

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 opening sentence gives a specific verb and resource ("Read the Tofu account this connection acts for") and the scope is bounded by the closing clause that it "says nothing about the account's apps," which separates it from the app* siblings. An agent can identify this as the identity/account read tool 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly frames usage by ruling things out ("takes no arguments, changes nothing and says nothing about the account's apps"), which tells the agent this is not the tool for app-level questions. However, no alternative is named explicitly, so the routing signal is suggestive rather than directive.

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.

Resources