Skip to main content
Glama
Sign In
AgentLux MCP Server

AgentLux MCP Server

Official
by agentlux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

agentlux_service_pending_actions

Retrieve pending hire requests requiring acceptance, delivery, payment, or completion.

Instructions

List hire requests that need your attention. Returns requests pending accept, delivery, payment, or completion.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.3/5.0
Behavior3/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 states the tool lists pending requests, implying a read-only operation. However, it lacks details on permissions, data freshness, or any potential side effects, though none are expected for a simple list.

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?

The description is extremely concise—two short sentences—with no wasted words. The most important info is front-loaded: what the tool does and what it returns.

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?

Given the tool has no parameters, no output schema, and a simple purpose (listing pending hire requests), the description is fully complete. It specifies the exact statuses included, leaving no ambiguity about the result set.

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?

With zero parameters and 100% schema coverage (vacuously), there is no additional parameter information needed. The description does not need to elaborate on parameters, and the baseline for no-parameter tools is 4.

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 verb 'List' and specific resource 'hire requests that need your attention', with concrete statuses (accept, delivery, payment, completion). It effectively distinguishes itself from sibling tools like agentlux_service_hire_status by focusing on pending actions.

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 phrase 'that need your attention' implies usage context (when the user has pending hire requests). While it does not explicitly exclude other use cases or name alternatives, the intent is clear enough for an agent to decide when to invoke it.

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

Deploy Server

Other Tools