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. Users with no ratings sort last under highest_rated. The website's Users tab opens on most_completed instead, so ask for most_completed to see the page a person sees; that sort breaks ties on the count by rating, then by username.
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
    • changedInput schema / properties / sort / description
      Previous value: -"Default highest_rated, the same default the website's Users tab opens on. Users with no ratings sort last under highest_rated."New value: +"Default highest_rated. Users with no ratings sort last under highest_rated. The website's Users tab opens on most_completed instead, so ask for most_completed to see the page a person sees; that sort breaks ties on the count by rating, then by username."
  2. 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"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe read-only, idempotent, non-destructive profile, and the description layers on non-obvious behavior: only verified accounts are returned, api_active true means software has used the account while false proves nothing, and the tool applies no ranking of its own. These are real data-semantics facts an agent could not infer from the schema or annotations.

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?

Purpose is front-loaded in the opening clause before the field inventory. It is a single dense paragraph and the 'Sort and filter as you like... nothing here ranks people for you' sentence is mildly redundant, but nearly every clause carries information.

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 return-shape burden and does so by enumerating the exposed facts (username, description, join date, rating, job counts, earnings, api_active). For a 6-param filterable list tool, an agent has everything needed to call and interpret it.

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%, so the schema already documents role, sort, limit, offset, rating, and search, including defaults and the website-vs-tool sort divergence. The description adds no further parameter syntax or format detail, 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 pins it to a concrete referent ('the Browse page's Users tab'). This clearly differentiates it from the single-entity sibling get_user and from browse_jobs, which lists jobs rather than people.

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 precise when-to-use: 'find someone to hire when you have no job to start from,' and explains why no other path works (a counterparty is otherwise only reachable via a job). It stops short of naming alternatives like get_user or browse_jobs for the reverse case, so it is strong context without explicit exclusions.

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