Skip to main content
Glama
Sign In

PeoplePerHour MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Cotlet: how to work in an app

cotlet_app_guide
Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For PeoplePerHour it covers these actions: Search projects, Get project brief, Search freelancers, Get freelancer profile, Search Offers, Get Offer, List categories, Get account, List my projects, Watch and unwatch projects, List watchlist, List, save and delete saved searches, List notifications, List WorkStreams.

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": "cotlet_app_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: PeoplePerHour.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: the call is free and consumes no browser session, and unknown apps degrade to a general method rather than failing. It does not describe the shape of the returned guidance, but that is a minor omission against the annotation coverage.

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 purpose and the call-before-first-step trigger are front-loaded, and the caveats (free, no session, general fallback) follow tightly. The trailing PeoplePerHour action enumeration is long but informative rather than redundant, though it bloats the paragraph and could be trimmed or split.

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?

For a guidance-retrieval tool with no output schema, the description covers the categories of content returned and the fallback behavior, which is enough for an agent to call it correctly. It leaves only the return format (prose vs. structured) unstated.

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%, so both optional parameters are already documented, making 3 the baseline. The description adds real meaning by enumerating what the PeoplePerHour app value unlocks (search projects, get brief, watchlist, saved searches, notifications, WorkStreams), which tells the agent the granularity expected in the app/task inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states concretely what the tool returns: which browser to use for the workspace, the sign-in link, the step-by-step method, the app's screens/menus/actions, notes, and dedicated tools. That is a specific, non-tautological purpose an agent can recognize. It only weakly separates itself from siblings such as cotlet_apps or the peopleperhour_* action tools, which it lists rather than contrasts.

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?

"Call it before the first browser step in an app" gives an explicit trigger point, and "Works for any web app; one outside Cotlet's catalog gets the general method" sets scope. It does not name a when-not condition or an alternative tool, so it falls short of full routing guidance.

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

All PeoplePerHour MCP Server and API by Cotlet 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