NOT FOR HUMANS

List NFH trait offers

list_trait_offers

Read-onlyIdempotent

Query OpenSea by 1–8 AND-combined traits. Results and hashes are unverified; decode and validate the full order before execution.

Input Schema

TableJSON Schema

Name	Required	Description
`next`	No	OpenSea pagination cursor from a prior response.
`limit`	No
`traits`	Yes	1–8 categorical traits, AND-combined.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	Yes
`status`	Yes
`provider`	Yes
`warnings`	Yes
`collectionSlug`	Yes
`providerPayload`	Yes
`requestedCriteria`	Yes
`collectionContract`	Yes
`providerOutputVerified`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedAug 23, 2026

changedInput schema / properties / traits / description

Previous value: -"One to eight categorical filters. Multiple traits are AND-combined."New value: +"1–8 categorical traits, AND-combined."

changedInput schema / properties / traits / items / properties / traitType / description

Previous value: -"Exact case-sensitive metadata trait name from nfh://renderer-spec, for example Personality or Memory Class."New value: +"Exact case-sensitive trait name from nfh://renderer-spec."

changedInput schema / properties / traits / items / properties / value / description

Previous value: -"Exact metadata trait value from nfh://renderer-spec, for example Deadpan or Persistent."New value: +"Exact trait value from nfh://renderer-spec."

removedOutput schema / properties / collectionContract / description
```
Removed value: -"A 20-byte EVM wallet or contract address."
```
removedOutput schema / properties / requestedCriteria / properties / traits / description
```
Removed value: -"One to eight categorical filters. Multiple traits are AND-combined."
```

removedOutput schema / properties / requestedCriteria / properties / traits / items / properties / traitType / description

Removed value: -"Exact case-sensitive metadata trait name from nfh://renderer-spec, for example Personality or Memory Class."

removedOutput schema / properties / requestedCriteria / properties / traits / items / properties / value / description
```
Removed value: -"Exact metadata trait value from nfh://renderer-spec, for example Deadpan or Persistent."
```

First observedAug 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds important beyond-annotation behavior by warning that results and hashes are unverified and must be decoded and validated before execution, which is valuable trust/safety context for an open-world data source.

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 with no filler. The first states what the tool does and the second adds an important safety caveat. Everything earns its place and the content is easy for an agent to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the read-only annotations, existing output schema, and parameter documentation, the description provides the essential context: source, filter shape, and validation caution. It does not need to restate return or pagination details because the schema and output schema cover those, making the definition largely complete for a listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description repeats the AND-combined and 1–8 trait constraints already present in the schema, but adds little about the 'next' cursor or 'limit' semantics. Since schema coverage is fairly high and the schema itself documents the parameters reasonably well, this is a minimum-viable score rather than a strong one.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action and resource: querying OpenSea for trait offers using 1–8 AND-combined traits. The tool's purpose is instantly understandable and is reasonably distinct from generic list/search tools, though it does not explicitly name or contrast sibling alternatives.

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?

The description conveys that this is the tool for listing OpenSea offers filtered by traits, which is clear contextual guidance. It does not explicitly state when not to use the tool or name alternatives like find_best_order or search, so it falls short of the 5-level guidance.

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

All NOT FOR HUMANS tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.