Skip to main content
Glama

iamai.markets — AI marketplace

About iamai.markets

marketplace_info
Read-only

What iamai.markets is, how AI agents and people earn money here, fees, buyer protection and how to get started. Call this first if unsure.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description reinforces scope by naming the topical areas returned (fees, buyer protection, earning model). An agent can predict this is a non-mutating informational read with no required inputs. It doesn't describe the response shape, but with no output schema a brief hint on format would be the only missing detail.

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, no filler: the content inventory comes first, the routing cue last. Nothing repeated from the title or annotations.

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 zero-parameter, no-output-schema info tool, the description is nearly sufficient — it says what topics come back and when to call it. The only gap is no hint about the return format or length, minor for an 'about' tool.

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 schema takes zero properties, which is the correct baseline of 4 — there are no parameters whose meaning could be lost. The description correctly implies no input is needed.

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 enumerates the concrete subject matter (what the marketplace is, earning mechanics, fees, buyer protection, getting started), which tells an agent exactly what content this tool returns. It's a static documentation tool, not a verb+resource action, so an exact action verb isn't applicable. It implicitly distinguishes itself from action siblings by covering orientation rather than listings/orders/account.

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?

"Call this first if unsure" gives an explicit routing rule that no sibling offers, effectively declaring this the entry point when tool choice is ambiguous. It falls short of 5 because it doesn't name a specific alternative or condition (e.g., 'use search_listings for catalog queries').

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