Skip to main content
Glama

iEscrow Marketplace (read-only)

Reputation of a seller

get_seller_profile
Read-onlyIdempotent

The real track record of an iEscrow account: completed trades, cancellations at fault, dispute rate, average star rating and whether their identity is verified. Use the seller.user_id from search_products_and_services. No account needed. There is no invented score: what you get is what happened.

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": {
      "user_id": "<user_id>"
    },
    "name": "get_seller_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, and the description still adds real value: no authentication required, and the framing that the returned data is raw historical fact rather than a derived score. It does not discuss rate limits or what happens for an unknown or inactive user_id.

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 valuable content — what is returned, where the id comes from, no auth — is front-loaded in four short sentences. The closing line 'There is no invented score: what you get is what happened' is marketing flavor that restates the opening 'real track record' and could be cut.

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?

With no output schema, the description correctly substitutes by listing the returned fields, and it covers the one required input's provenance and the auth situation. Missing only edge-case behavior (invalid or unknown seller id) for a simple single-parameter read 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?

Schema coverage is 0%, so the description must carry the parameter meaning, and it partially does by pinning the value to 'seller.user_id from search_products_and_services'. It adds no type or range cues, though, and the schema's integer ceiling/positive constraint is unaddressed; the provenance hint is the only added semantics for the single argument.

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?

Names the resource ('track record of an iEscrow account') and enumerates exactly what comes back: completed trades, cancellations at fault, dispute rate, average star rating, identity verification. That is far more specific than the title and clearly distinct from search_products_and_services / get_product_or_service / get_quote. It does not explicitly contrast with a sibling, which keeps it at 4 rather than 5.

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?

Gives a concrete calling condition and the source of the argument: 'Use the seller.user_id from search_products_and_services', which establishes the chaining pattern. 'No account needed' removes an anticipated prerequisite. No when-not-to-use or failure-case guidance is offered, so it stops short of 5.

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.