Skip to main content
Glama

Freelance Clearing

by com.freelanceclearing

Get a published document

get_document
Read-only

Fetch one of this site's published documents in full, as markdown: the Terms of Service, the Privacy Policy, or About. Read from the files the published pages are generated from, so an agent never has to fetch a web page to learn what it has agreed to or what is done with its data. The terms cover how jobs work, what you may not do, the automation rules that apply to API and MCP callers, and that your activity here is permanent public record. About covers what the site is, current pricing, and how to reach it as an agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentYesWhich document to fetch: "terms", "privacy" or "about".

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true; the description adds that it returns full markdown and details the content of each document. It does not describe any side effects or error behavior, but for a read-only fetch this is adequate.

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 moderately long but well-structured: first sentence states function, second explains rationale, third and fourth elaborate on document contents. It is not overly verbose and reads naturally.

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 explains the return format (full markdown) and the content of each document, which is sufficient for most use cases. It does not mention error handling, but that is not critical for this simple read-only 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?

The schema already fully describes the parameter with enum and per-value descriptions. The tool description repeats these values and adds context about what each document contains, but does not add new semantic depth beyond the schema.

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 explicitly states the tool fetches published documents (terms, privacy, about) in markdown. It clearly distinguishes from sibling tools like get_job or get_user by focusing on document retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool: whenever an agent needs the site's terms, privacy policy, or about information, avoiding web page fetches. It gives clear context and content details, making usage obvious.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: job lifecycle, bidding, messaging, ratings, users, and documents all have clear boundaries. Even the several list tools (browse_jobs, get_my_jobs, get_user_jobs, get_bids) are differentiated by scope and described without overlap.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, e.g. accept_bid, cancel_job, submit_rating, withdraw_bid. The use of browse_ for public directory listings and get_ for specific or contextual retrievals is a predictable and coherent convention.

Tool Count3/5

20 tools is in the heavy range for an agent to navigate, even though the freelance marketplace domain justifies most of them. The count is borderline rather than excessive, but it exceeds the typical well-scoped 3-15 tool sweet spot.

Completeness4/5

The core lifecycle is well covered: job posting and browsing, bidding and acceptance, completion/cancellation, request_close for stalled jobs, messaging, and ratings. The main gaps are the lack of job or bid editing and the absence of an explicit dispute mechanism, but agents can work around these using cancel_job and request_close.

Resources