Skip to main content
Glama

Freelance Clearing

by com.freelanceclearing
OverviewDiscussionsAdmin

Get a published document

get_document
Read-onlyIdempotent

Fetch one of this site's published documents in full, as markdown: Terms of Service, Privacy Policy, About, or Payments & Trust. 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. Payments & Trust sets out the fees, what a cancellation returns, and when money moves, and forms part of the terms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentYesWhich document to fetch: "terms", "privacy", "about", or "payments-and-trust".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / document / description
      Previous value: -"Which document to fetch: \"terms\", \"privacy\" or \"about\"."New value: +"Which document to fetch: \"terms\", \"privacy\", \"about\", or \"payments-and-trust\"."
    • changedInput schema / properties / document / enum
      Previous value: -[
-  "terms",
-  "privacy",
-  "about"
-]New value: +[
+  "terms",
+  "privacy",
+  "about",
+  "payments-and-trust"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral context: it reads from source files rather than a rendered web page, returns the full document as markdown, and avoids the need to fetch HTML. This goes beyond the structured annotations without contradicting them.

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 longer than average, but each sentence contributes meaningful context about document contents and why the tool exists. It is front-loaded with the core purpose and then expands on use cases, so the length is justified rather than wasteful.

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?

The tool has one parameter, no output schema, and no close sibling tools. The description fully covers what the tool returns (full markdown), what each document contains, and why it is useful. An agent has everything needed to select and invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents the single parameter with a full enum and description, so baseline is 3. The description adds semantic meaning by summarizing what each document covers (terms, About, Payments & Trust), helping an agent choose the correct enum value based on the information it needs.

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 names a specific verb and resource: fetching one of four site documents in full as markdown. It explicitly enumerates the documents and explains what each contains, making the tool's purpose unambiguous and distinguishing it from any page-fetching alternative.

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?

The description provides clear context for when to use the tool: when an agent needs the site's published legal or policy documents without fetching a web page. It does not explicitly state when not to use it or name alternative sibling tools, but no sibling serves a similar document-retrieval purpose, so the guidance is adequate.

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