Skip to main content
Glama

get_worker

Read-onlyIdempotent

Return one worker's public profile and reputation. ask_rate_minor is the worker's enforced minimum per-task price in minor units and ask_rate_basis is per_task. rate_card entries are advisory asks for labeled work; when the task fits a label, offer at least that entry's rate_minor. Only the general ask is enforced by the offer endpoint. live_now reports whether the worker is presently live; live_until is the timestamp when that explicit presence expires.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
worker_idYesThe worker's id, as returned by search_workers.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleNo
ratingNo
skillsNo
currencyNo
live_nowNo
languagesNo
rate_cardNo
worker_idNo
live_untilNo
has_vehicleNo
rating_countNo
ask_rate_basisNo
ask_rate_minorNo
completed_tasksNo
verification_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / worker_id / description
      Added value: +"The worker's id, as returned by search_workers."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "ask_rate_basis": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Ask Rate Basis"
      +    },
      +    "ask_rate_minor": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Ask Rate Minor"
      +    },
      +    "completed_tasks": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Completed Tasks"
      +    },
      +    "currency": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Currency"
      +    },
      +    "handle": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Handle"
      +    },
      +    "has_vehicle": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Has Vehicle"
      +    },
      +    "languages": {
      +      "anyOf": [
      +        {
      +          "items": {},
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Languages"
      +    },
      +    "live_now": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Live Now"
      +    },
      +    "live_until": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Live Until"
      +    },
      +    "rate_card": {
      +      "anyOf": [
      +        {
      +          "items": {},
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Rate Card"
      +    },
      +    "rating": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Rating"
      +    },
      +    "rating_count": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Rating Count"
      +    },
      +    "skills": {
      +      "anyOf": [
      +        {
      +          "items": {},
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Skills"
      +    },
      +    "verification_status": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Verification Status"
      +    },
      +    "worker_id": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Worker Id"
      +    }
      +  },
      +  "title": "WorkerOut",
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare the operation safe and read-only, and the description adds significant behavioral nuance: it explains that ask_rate_minor is enforced, rate_card entries are advisory, and live_now/live_until describe temporary presence. This goes well beyond the annotations and gives agents precise rules for interpreting the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the primary purpose, then efficiently clarifies the most error-prone semantic distinctions (enforced vs. advisory rates, live presence fields). Every sentence adds necessary operational detail; there is no filler.

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 a single well-documented parameter, strong safety annotations, an output schema present, and no nested objects, the description is complete for safe invocation. The added rate-card and live-status semantics fill the gaps that would otherwise be ambiguous, making the tool fully usable.

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 input schema fully documents the single parameter worker_id, including where to obtain it ('as returned by search_workers'). The description adds no additional meaning for this parameter itself, so the schema carries the full burden. Baseline 3 is appropriate.

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 clearly states the tool's function: returning one worker's public profile and reputation. It uses a specific verb ('return') with a specific resource ('one worker's public profile'), and the term 'one' differentiates it from list/search tools like search_workers and get_worker_location.

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 implies usage context: it returns a single worker's profile, and the parameter description notes worker_id comes from search_workers, which suggests a search-then-fetch workflow. However, it does not explicitly name alternatives or state when not to use this tool versus a sibling such as get_worker_location.

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.