Skip to main content
Glama

fairagent_get_agent

Read one FairAgent NFT: owner, image, traits, ERC-8004 link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tokenId": "<tokenId>"
    },
    "name": "fairagent_get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; 'Read' signals a non-mutating lookup, and the field list hints at the response shape. It does not disclose what happens for a nonexistent tokenId, where the data comes from (on-chain vs indexer), or whether the call is cached/rate-limited.

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?

A single front-loaded sentence with a compact field enumeration; every element earns its place and nothing is redundant.

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?

For a simple single-token read with no output schema, listing the returned fields compensates well for the missing response definition. Minor gaps remain around lookup failure behavior and chain/network context.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions 'tokenId' — it only says 'one ... NFT'. An agent must infer that the single required integer is the NFT's token identifier, and nothing is said about valid ranges beyond the schema's minimum of 1.

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 gives a specific verb ('Read') and resource ('one FairAgent NFT') and enumerates the returned fields (owner, image, traits, ERC-8004 link), so an agent can tell it apart from build_mint_tx (constructs a transaction) and info (general metadata). It stops short of explicitly contrasting with those siblings, keeping it just below a top score.

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

Usage Guidelines3/5

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

Usage is only implied: 'Read one FairAgent NFT' suggests fetching details for a specific token, but there is no stated condition selecting it over fairagent_info or any prerequisite (e.g., needing a known tokenId first). No exclusions or when-not-to-use guidance is provided.

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