Skip to main content
Glama

agentnet_run_guest_task

Run a free bounded text task. Supply only non-sensitive text.

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": {
      "skill": "<skill>",
      "text": "<text>"
    },
    "name": "agentnet_run_guest_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesNon-sensitive text.
skillYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is partly covered, but readOnlyHint=false signals a non-read operation that the description never explains. "Bounded" and "free" hint at limits and cost without stating them (the 1000-character cap is only in the schema), and there is no mention of side effects, rate limits, or what the run produces.

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?

Two short, front-loaded sentences with no filler, so nothing needs trimming. However, the brevity reflects under-specification rather than disciplined conciseness — the space saved is space the agent needs filled.

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

Completeness2/5

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

For a tool whose entire behavior depends on a two-value skill enum, the definition explains neither skill, has no output schema to fall back on, and gives no sense of what a successful run returns. An agent could call it but could not predict or validate the outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the skill enum has no description anywhere, and the description does not compensate by explaining what text-insights or sha256 do. The one piece of text semantics offered ("non-sensitive text") merely repeats the schema's own parameter description.

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?

"Run a free bounded text task" largely restates the name agentnet_run_guest_task, swapping "guest" for "free" and adding an unexplained "bounded." It never says what a "text task" actually does, and the two available skills (text-insights, sha256) — which are the real substance of the operation — are never mentioned or distinguished from the sibling tools.

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

Usage Guidelines2/5

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

"Supply only non-sensitive text" is an input constraint, not when-to-use guidance. There is no statement of when this tool should be chosen over agentnet_guest_capabilities or agentnet_status, nor any guidance on which skill to pick for which goal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources