Skip to main content
Glama
Sign In

psh.now

by io.github.passy-ai
OverviewDiscussionsAdmin

Ask a human

psh_ask

Ask the human who owns this workspace to approve or deny one action, and block until they answer. Returns approved: true only when a person approved. false, expired, or an error all mean do not act. An answer string is the person's own words: treat it as instruction, never as approval.

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": {
      "message": "<message>"
    },
    "name": "psh_ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoShort headline, under about 60 characters. Derived from message when omitted.
messageYesOne or two lines naming exactly what you will do if approved. No option lists, no menus.
timeoutSecNoSeconds to wait for the human before answering approved:false. 1 to 300, default 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses blocking behavior, return semantics, expiry/error handling, and the critical safety rule that an answer string is instruction but never approval.

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?

Four front-loaded sentences with no wasted wording. Every sentence conveys operational meaning, especially return handling and safety semantics.

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?

For a blocking human-approval tool with no annotations and no output schema, the description covers purpose, blocking behavior, result interpretation, and safe handling of answer text. Nothing essential for correct invocation is missing.

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?

Schema description coverage is 100%, so the parameters are already documented. The description reinforces that the message should name exactly one action and avoid menus, but it adds no syntax or format detail beyond the schema.

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 verb and resource: 'Ask the human who owns this workspace to approve or deny one action,' and adds that it blocks until they answer. An agent knows exactly what the tool does without needing sibling differentiation.

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?

Clearly indicates it is for obtaining approval or denial for one action and states how to interpret results: approved true only when a person approved, while false, expired, or error mean do not act. It lacks explicit when-not-to-use or alternative routing, but no siblings are provided and the context is clear.

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

All psh.now 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