Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Top 10 tokenized real estate tokens (free)

free_tokenized_real_estate
Read-only

FREE. Top 10 RWA property tokens (RealT RealTokens on Gnosis) by on-chain market cap: token, contract, city, state, on-chain price. tokenized_real_estate ($0.005) adds every property, supply, RMM collateral and filters.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds that the tool is free, specifies the chain (Gnosis) and token type (RealT RealTokens), and lists returned fields—useful context beyond the schema. It does not cover data freshness or rate limits, but these are minor given the fixed top-10 nature.

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?

Two sentences, front-loaded with 'FREE' and the core purpose. Every clause carries information: ranking method, field list, and the paid alternative. No fluff.

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?

No output schema exists, but the description lists the returned fields (token, contract, city, state, on-chain price) and explains the scope (top 10 by market cap). The paid alternative is mentioned, so an agent has everything needed to call this tool correctly.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and the schema requires no input.

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 specifies a concrete retrieval task: top 10 RWA property tokens (RealT RealTokens on Gnosis) ranked by on-chain market cap, and lists the exact fields returned. It clearly distinguishes itself from the sibling tokenized_real_estate by noting the latter's expanded data set and cost.

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?

It explicitly names the paid alternative (tokenized_real_estate, $0.005) and states what that tool adds (every property, supply, RMM collateral, filters). This gives an agent a clear decision criterion: use this for a free top-10 summary, use the other for comprehensive data.

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

All Scrapling x402 Data Store 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