Skip to main content
Glama

Get my offers

get_my_offers
Read-onlyIdempotent

List the connected person's offers on Fabrica (Sepolia Testnet), across every wallet on their account: received, the offers waiting on their properties (per property, highest first, with whether the property is under a loan and the property page where an offer is accepted), and made, the offers they placed on other properties. Each offer has its USD price and amount, buyer, expiry, and expiringSoon when it ends within 3 days. Live offers only unless status is 'all'. Needs the connection's portfolio:read grant. get_land_order_book reads any one property's listings and offers.

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_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNo'both' (default), 'made': offers this person made, 'received': offers waiting on their properties
statusNo'active' (default): live offers only. 'all': also expired, canceled and filled ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnly, idempotent, non-destructive), and the description adds real substance on top: the portfolio:read grant requirement, per-property grouping with highest-first ordering, a 'under a loan' flag, the property page where an offer is accepted, and the 3-day expiringSoon threshold. These are behavioral details an agent could not infer from the annotations.

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-loads the verb and resource, then layers side definitions, return fields, defaults, and the sibling alternative. Dense but each clause carries information; the nested parentheticals make it slightly harder to scan than an ideal 5.

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?

There is no output schema, so the description carries the return-value burden and does: it names the fields per offer (USD price, amount, buyer, expiry, expiringSoon) and the grouping and ordering. With permission requirements and sibling routing covered, nothing material 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?

Schema coverage is 100%, so the baseline is 3, but the description adds interpretation of the return shape for each side value — 'received' as offers waiting on their properties, 'made' as offers they placed elsewhere — which clarifies what each enum selection actually yields. It also restates the 'all' semantics for status, reinforcing the schema rather than merely repeating it.

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 verb and resource — listing the connected person's offers on Fabrica — and enumerates both collections it covers (received, made) and the wallet scope. It explicitly differentiates itself from the sibling get_land_order_book, so an agent can pick between them without opening either 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?

Gives clear context: use this for the account-wide view across every wallet, and use get_land_order_book to read any single property's listings and offers. It also states the default filter behavior ('live offers only unless status is all'). No explicit exclusions or prerequisites beyond the required grant, so not quite 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.