Skip to main content
Glama

nudgeonly_api

Classify noisy event text into painpoint hints and simple-English nudge summaries to identify issues like stale acknowledgments or unclear ownership.

Instructions

Run 👉Nudge, the PinballWake NudgeOnlyAPI worker, through OpenRouter free routing. Use only for painpoint hints and simple-English nudge summaries. It cannot merge, close, approve, assign ownership, mark done, or set source-of-truth state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoOpenRouter API key. Optional when OPENROUTER_API_KEY is set in the environment.
event_textYesNoisy event, signal, handoff, or status text for 👉Nudge to classify.
contextNoOptional local context. Keep it small and non-secret.
painpoint_hintNoOptional hint such as stale_ack, duplicate_wake, unclear_owner, noisy_thread, or missing_proof.
source_idNoOptional upstream event, dispatch, PR, issue, or wake identifier for trace evidence.
source_urlNoOptional upstream URL for trace evidence.
modelNoOpenRouter model ID. Default: liquid/lfm-2.5-1.2b-instruct:free. Use openrouter/free only when auto-rotation is desired.
allow_paidNoExplicit opt-in required for paid or unknown OpenRouter model IDs. Free :free models do not need this.
max_tokensNoMaximum output tokens. Hard capped at 500. Default: 260.
Behavior3/5

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

With no annotations, the description carries full burden. It discloses free routing and limitations, but lacks details on auth requirements (beyond API key), error behavior, rate limits, or response meaning. Partial transparency.

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 core purpose, then usage guidance and limitations. Every sentence adds value with no redundancy.

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?

Description covers purpose and constraints but does not explain expected output (no output schema) or how parameters interact. Adequate for a simple classifier summarizer, but incomplete for a 9-parameter tool.

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 coverage is 100%, so baseline is 3. The description mentions 'painpoint hints' aligning with one parameter but adds no significant semantics beyond the schema's parameter descriptions.

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 the tool runs the NudgeOnlyAPI worker through OpenRouter free routing, specifies its use for 'painpoint hints and simple-English nudge summaries', and explicitly lists what it cannot do (merge, close, approve, etc.), distinguishing it from related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use (painpoint hints and nudge summaries) and when not to use (cannot perform state-changing actions like merge or approve), giving the agent clear boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'

If you have feedback or need assistance with the MCP directory API, please join our Discord server