Skip to main content
Glama

workman.rent — humans for real-world checks

List ready-made task templates

list_task_templates
Read-onlyIdempotent

Catalogue of ready-made task templates (call_check, storefront_photo, shelf_price_check, store_open_check). Each has a result spec (checklist questions, minimum photos, done-when), a recommended and minimum budget in USDC, the executor skill, the location type and a default deadline. Create a task from one with create_task { template_id, purpose, place or lat/lng, + your own description where required }. No account needed. Read-only. Returns: { templates: [{ id, title, summary, recommended_budget_usdc, min_budget_usdc, required_skill, location_type, remote, default_deadline_hours, result_spec, required_fields }] }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_task_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly/idempotent/destructive=false, and the description adds genuinely new context: no authentication required, and what each template carries (result spec with checklist questions, minimum photos, done-when, recommended/minimum budget in USDC, executor skill, location type, default deadline). 'Read-only' merely restates the annotation, so it is not a full 5.

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?

Front-loaded with the resource and the template ids, then the follow-up call, then the return shape. Dense but each sentence carries information; the parenthetical template-id list and the long field enumeration make it slightly heavy, though nothing is truly wasted.

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?

There is no output schema, and the description compensates by spelling out the exact return shape ({ templates: [{ id, title, summary, recommended_budget_usdc, ... }] }). Combined with zero parameters and annotations covering safety, an agent has everything needed to call and consume this tool.

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 tool takes zero parameters, so the baseline is 4. The description goes further by explaining what a template_id represents and which companion fields create_task needs, which is useful meaning even though those parameters belong to the sibling tool.

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 resource ('Catalogue of ready-made task templates') and enumerates the concrete template ids (call_check, storefront_photo, shelf_price_check, store_open_check), so an agent knows exactly what it gets without opening anything else. The name, title, and description align with no ambiguity.

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 explicitly routes the agent forward: 'Create a task from one with create_task { template_id, purpose, place or lat/lng, ... }', and notes 'No account needed.' It gives clear context for use but does not state any when-not-to-use condition or tradeoff against alternatives.

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.

Resources