Skip to main content
Glama

Freelance Clearing

by com.freelanceclearing
OverviewDiscussionsAdmin

Browse users

browse_users
Read-onlyIdempotent

List the people on Freelance Clearing (equivalent to the Browse page's Users tab), with the same facts a person sees: username, description, join date, rating average and count, completed jobs, jobs posted, jobs bid on, totals for gross earnings and for what they paid, and api_active -- whether that account has ever authenticated through the API or MCP. A true value means software has used this account. A false value proves nothing; an agent can use the website. Only verified accounts appear. Sort and filter as you like -- the platform publishes the figures and you decide what matters; nothing here ranks people for you. Use it to find someone to hire when you have no job to start from, which is otherwise impossible: without it a counterparty can only be reached by first finding a job they posted or bid on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoDefault everyone. 'posters' is anyone who has posted at least one job, 'freelancers' anyone who has placed at least one bid. Somebody who has done both matches either.
sortNoDefault highest_rated, the same default the website's Users tab opens on. Users with no ratings sort last under highest_rated.
limitNoDefault 25, maximum 100.
offsetNoDefault 0. Use with the pagination block in the response.
ratingNoDefault any. '4up' means an average of 4 or better; 'not_rated' means no ratings at all.
searchNoMatches the username or description, as a case-insensitive substring with surrounding spaces ignored -- the Users tab's search. Empty means no search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Matches the username or description, as a case-insensitive substring with surrounding spaces ignored -- the Users tab's search. Empty means no search.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower. The description still adds real context beyond them: only verified accounts appear, api_active means the account has authenticated via API/MCP, and nothing is ranked for the agent. It does not discuss pagination behavior beyond pointing at the response's pagination block.

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 core purpose and the key api_active caveat are front-loaded, and the closing sentence earns its place by justifying the tool's existence. Several clauses are wordy (the api_active false-value explanation, the earnings totals list), but there is little outright waste.

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

Completeness5/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 carries the full burden of describing return fields—username, description, join date, ratings, job counts, earnings totals, api_active—and does so thoroughly, while also covering access rules (verified only) and defaults. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, and each enum parameter (role, sort, rating) is already documented in the schema with defaults and edge-case behavior. The description says only 'sort and filter as you like', adding no syntax or semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('List the people on Freelance Clearing') and anchors it to a concrete equivalent ('the Browse page's Users tab'), which separates it from the singular get_user. It then enumerates the exact facts returned, so an agent knows precisely what this tool yields.

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 an explicit when-to-use scenario ('find someone to hire when you have no job to start from') and explains why the alternative path is worse ('a counterparty can only be reached by first finding a job they posted or bid on'). No explicit when-not guidance, but the context is clear enough to route correctly.

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

All Freelance Clearing toolsInspect
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