Skip to main content
Glama
Sign In
timps-swarm

timps-swarm

by Sandeeprdy1729
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

timps_win_loss_analyst

Analyze won/lost deals to surface real reasons—pricing, champion, timing, competitor, fit—and get recommendations for sales coaching and product fixes.

Instructions

Analyse a set of won/lost deals to surface the real reasons — pricing, champion, timing, competitor, fit — and recommend sales-coaching and product fixes.

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

Input Schema

NameRequiredDescriptionDefault
requestNoPlain-English task or context for the agent.
languageNoPrimary programming language (default: python).python

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It does not mention whether the tool is read-only, has side effects, or requires specific permissions. This lack of transparency could mislead an agent.

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 a single, dense sentence that packs all essential information without fluff. It is well-structured and immediately comprehensible.

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?

The description covers the tool's purpose but does not specify output format, return value, or any additional context. Given the lack of an output schema, this leaves some ambiguity about what the agent can expect from the tool.

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?

Parameter descriptions are minimal: 'request' is described as 'Plain-English task or context' and 'language' as 'Primary programming language'. They add little beyond the schema and do not explain how they affect the tool's behavior or output.

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's function: analyzing won/lost deals, surfacing reasons (pricing, champion, timing, competitor, fit), and recommending sales-coaching and product fixes. It is specific and distinct from typical analytics tools.

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?

The description implies usage for win/loss analysis but does not explicitly mention when to use this tool versus alternatives or any exclusions. It lacks guidance on selecting this over similar analytical 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