Skip to main content
Glama
Sign In

Fabrica (Sepolia testnet)

by land.fabrica
OverviewDiscussionsAdmin

Get my Fabrica account

get_my_account
Read-onlyIdempotent

Get the connected person's own Fabrica account on Sepolia Testnet: their email, their linked accounts (every wallet address on the account, each listed once), their verification status, the dollars (USDC) each account holds with a Cash out link on fabrica.land from a dollar up, and what this connection may read (its scopes and when its access token expires). Takes no input: it always answers for the person who connected, never for anyone else.

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. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds real value by disclosing the exact returned fields, the dedup rule ('each listed once'), the Cash out link threshold ('from a dollar up'), and the token-expiry scopes. It does not mention failure modes or whether balances are live vs cached, which keeps it below 5.

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 core action and network, then the return contents, then the no-input constraint. It is a single long sentence packing several parentheticals, which is dense but every clause carries information; a short bulleted return list would read faster.

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?

With no output schema and no parameters, the description must carry the return shape, and it does: identity fields, linked wallets, verification, dollar balances, and session scopes/expiry. An agent can decide to call it and interpret the result without further documentation.

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?

Zero parameters, so the baseline is 4. The description reinforces this usefully ('Takes no input') and confirms the implicit subject is always the authenticated caller, which prevents an agent from hunting for a user-id argument.

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?

Names a specific verb and resource ('Get the connected person's own Fabrica account on Sepolia Testnet') and enumerates the payload contents: email, linked accounts, verification status, USDC balances, scopes and token expiry. The 'connected person's own' framing clearly separates it from the sibling get_my_loans/offers/properties tools, which cover different resources.

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?

Explicitly states the selection boundary: 'Takes no input: it always answers for the person who connected, never for anyone else,' which tells an agent this is the identity/account-context call rather than anything parameterized. It stops short of naming an alternative for looking up another user's account, so it does not reach a 5.

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

All Fabrica (Sepolia testnet) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources