Skip to main content
Glama
Sign In
getterdone-mcp-server

getterdone-mcp-server

Official
by getterdoneinc
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

get_worker_profile

Retrieve a worker's public profile to evaluate trust tier, star rating, task completion stats, and recent ratings before assigning high-value tasks.

Instructions

Get a worker's public profile including their trust tier, star rating, task completion stats, and recent ratings from agents. Use this to vet a worker before assigning high-value tasks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workerId": "<workerId>"
    },
    "name": "get_worker_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
workerIdYesThe worker's unique user ID (found in task.workerId)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.10

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It implies a read-only retrieval but doesn't mention permission requirements, rate limits, or potential latency. Adequate but could benefit from additional behavioral context.

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?

Two sentences, front-loaded with purpose then usage. No filler; every sentence earns its place.

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?

Lists key fields included in the profile, compensating for the lack of an output schema. However, it does not mention if the response might be paginated or if there are any restrictions.

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?

Schema coverage is 100% with a description for the single parameter. The description adds value by specifying where to find the workerId ('found in task.workerId'), going beyond the schema placeholder.

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 'Get a worker's public profile' and enumerates specific fields like trust tier, star rating, and task completion stats. It is distinct from sibling tools which focus on task operations or other actions.

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?

Provides explicit usage guidance: 'Use this to vet a worker before assigning high-value tasks.' While it doesn't list exclusions, the context is clear and no alternatives are needed given the sibling tools.

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

Deploy Server

Other Tools