Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pclas_info

Retrieve service information and terms for a predictive cognitive-load anticipation system that forecasts agent overload and plans proactive task reassignment across fleets.

Instructions

[FREE] PCLAS - Predictive Cognitive-Load Anticipation System for agent fleets. Forecasts each agent's workload over a horizon (Holt exponential smoothing on provided history, or deterministic synthesis), detects overload peaks BEFORE they happen, and computes a proactive task reassignment plan moving low-priority heavy tasks to agents with headroom. Verdicts: STABLE (no overload), REASSIGN (plan clears all peaks), CRITICAL (overload survives reassignment). This tool returns service info and terms. The paid forecast endpoint is https://agentpaystore.com/pclas/api/forecast (POST, $0.05 USDC via

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose that the tool is free ('[FREE]') and separates that from the $0.05 USDC paid endpoint, which is genuinely useful. It says nothing about what the returned info/terms contain, whether any auth is needed, or whether the terms have implications for calling the paid endpoint.

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 functional intent is buried behind a multi-clause product pitch, and the description is truncated mid-sentence ('$0.05 USDC via '), which leaves the payment/access instructions incomplete. The key sentence about what this tool actually returns should be front-loaded rather than appended.

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?

For a zero-parameter info tool without an output schema, the description should describe what 'service info and terms' means in practice (pricing, endpoints, capabilities). Instead it describes the downstream forecast product and leaves the return content unspecified.

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 takes zero parameters and the schema is fully specified, so there is nothing for the description to disambiguate. Baseline 4 applies.

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

Purpose3/5

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

The description spends most of its length pitching the PCLAS forecasting service (Holt smoothing, peak detection, reassignment plans, verdicts) and only states the tool's actual action late: 'This tool returns service info and terms.' An agent skimming the opening could mistake this for the forecasting tool itself, which is a separate paid endpoint.

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

Usage Guidelines3/5

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

Usage is only implied via the pointer to the paid forecast endpoint at agentpaystore.com/pclas/api/forecast, suggesting this is the discovery/terms step before a paid POST. There is no explicit when-to-use statement, no when-not-to-use, and no comparison to the many sibling '*_info' tools.

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