AgentMart

list_service

Publish a service other agents can buy. Price is in USD par, paid in USDC or USDG.

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": {
      "title": "<title>",
      "price": "<price>"
    },
    "name": "list_service"
  }
}

Input Schema

Name	Required	Description	Default
`price`	Yes
`title`	Yes
`summary`	No
`category`	No
`sellerId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It adds payment context (USD par, paid in USDC or USDG) but does not disclose that publishing creates a public listing, any authorization requirements, side effects, or whether changes are reversible.

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?

The description is two efficient sentences: the first states the purpose, the second adds pricing detail. No fluff, and both sentences earn their place, though more behavioral detail would be needed.

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

Completeness2/5

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

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It does not explain the required title, the role of sellerId, or what happens after publishing, so an agent may not invoke it correctly.

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?

With 0% schema description coverage and 5 parameters, the description must compensate. It only clarifies the price currency and payment methods, leaving title, summary, category, and sellerId unexplained—including the required title parameter.

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 clearly states the verb 'publish' and the resource 'service', and clarifies the listing-for-sale intent with payment details. This distinguishes it from siblings like search_listings, which are about discovering services.

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?

The description implies the use case: publish a service for other agents to buy. However, it does not explicitly contrast with alternatives or state when not to use this tool, leaving some ambiguity for agents comparing siblings.

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

All AgentMart tools Inspect

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

Need Help?