Skip to main content
Glama
Sign In

PeoplePerHour MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

List notifications in PeoplePerHour

peopleperhour_list_notifications
Read-onlyIdempotent

List notifications in the user's own PeoplePerHour account from ChatGPT, Claude or any AI agent. Returns how to do it in PeoplePerHour step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's PeoplePerHour Cloud Browser. PeoplePerHour's official API: PeoplePerHour has no public API and no developer docs (checked 12 Oct 2026).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already mark it read-only, non-destructive, and idempotent, and the description adds useful context: it opens nothing by itself and only returns procedural guidance. It also discloses that PeoplePerHour has no public API, which is valuable behavioral context beyond the annotations.

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

Conciseness3/5

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

The description is reasonably front-loaded but includes filler such as "from ChatGPT, Claude or any AI agent" and repeats the no-public-API point. The core warning that it only returns instructions is present but sits after a potentially misleading "List notifications" opening.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters, rich annotations, and no output schema, the description explains the return as step-by-step screens, buttons, and fields. However, it does not fully resolve the mismatch between the tool name and its actual guide-like behavior, leaving an agent uncertain whether it retrieves notifications or instructions.

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 has zero parameters, so there is no parameter semantics burden. The schema is fully described by its emptiness, and the description adds no misleading parameter information.

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

Purpose2/5

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

The name and title say "List notifications," but the description says the tool returns step-by-step instructions and opens nothing by itself. That redefines the tool as a how-to guide rather than an actual notification-listing operation, which can mislead an agent selecting it.

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 clearly says to use the cotlet_browser_* tools in the user's PeoplePerHour Cloud Browser after receiving the steps. It gives a concrete alternative workflow, though it does not state when not to use this tool versus cotlet_app_guide or other guide tools.

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