Skip to main content
Glama

My Fold account

get_my_account
Read-onlyIdempotent

Only call this when the customer asks about their own Fold account, saved details or orders — it requires their connected Fold account and asks them to sign in. Prices, ZIP coverage, estimates and guest orders work without signing in (get_pricing, check_service_zip, get_estimate, book_residential_pickup). Returns their saved addresses (with gate code / access notes), whether a card is on file, Fold credit balance, Fold Club membership, laundry care preferences (detergent, water temperature, special instructions) and recurring pickups. book_my_pickup uses these saved details.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds information they cannot convey: the tool requires an authenticated/connected Fold account and prompts a sign-in, so an agent can anticipate an auth failure path. It also discloses the concrete payload an agent will receive (saved addresses including gate codes and access notes, card-on-file flag, credit balance, Club membership, care preferences, recurring pickups) and how book_my_pickup consumes it.

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?

Front-loaded with the when-to-call condition and the sign-in prerequisite before the alternatives and the return-value inventory, with no filler. The second half is a long comma-separated enumeration, which is dense though each item is informational.

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?

Although there is no output schema, the description enumerates the return fields in enough detail (including sensitive items like gate codes and credit balance) that an agent can decide whether it has the answer in hand. Auth prerequisites, exclusions, and the downstream consumer (book_my_pickup) are all covered.

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 no parameters, so the baseline is 4 and there is no schema semantics the description needs to compensate for. However, the description says nothing explicit about the account being identified implicitly by the session — an agent must infer that from 'their connected Fold account'.

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?

States a specific resource and scope ('their own Fold account, saved details or orders') and explicitly enumerates what the tool returns, so an agent knows exactly what it gets. It is clearly distinguishable from the account-agnostic siblings (get_pricing, check_service_zip, get_estimate, book_residential_pickup) which it names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit when-to-call trigger ('only call this when the customer asks about their own Fold account...'), an explicit when-not (prices, ZIP coverage, estimates, guest orders), and names the specific alternative tools for each excluded case. There is a clear prerequisite (signed-in connected account) that gates use.

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