Skip to main content
Glama
Sign In
timps-swarm

timps-swarm

by Sandeeprdy1729
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

timps_dispatch

Automatically matches any plain-English request to the appropriate specialist agent and executes it immediately, solving issues like WiFi drops, slow laptops, or broken Python environments without manual agent selection.

Instructions

Auto-detect the best TIMPS agent for any plain-English request and run it immediately. Use this when unsure which agent to pick. Examples: 'my wifi keeps dropping', 'why is my laptop slow', 'broken python environment', 'organize my downloads'.

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": {
      "request": "<request>"
    },
    "name": "timps_dispatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesThe user's plain-English request or complaint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

A3.9/5.0
Behavior2/5

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

No annotations exist, so description must handle transparency. It says 'run it immediately' implying execution but doesn't disclose side effects, potential dangers, or whether it may trigger destructive actions. Lacks details on error handling or what happens after dispatch.

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 plus examples, zero filler. Front-loaded with action and usage guidance, ideal for quick reading.

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?

Adequate for a simple one-parameter dispatcher: states what it does and when to use. However, lacks discussion of output, asynchronous behavior, or limitations like inability to detect certain requests. Given no annotations or output schema, could be more thorough.

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?

Schema already describes 'request' as 'plain-English request or complaint', and description repeats that and adds concrete examples. This provides practical context beyond schema, enriching parameter understanding.

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?

Clear verb 'auto-detect' and resource 'best TIMPS agent', explicitly states it runs the agent. Distinguishes from sibling agents by being the dispatch mechanism. Examples reinforce purpose.

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?

Explicitly says 'Use this when unsure which agent to pick', providing a direct decision criterion. Includes examples of typical requests but doesn't clearly state when not to use it or mention alternatives beyond 'which agent to pick'.

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