Skip to main content
Glama
Sign In
weeek-mcp

weeek-mcp

by MaxViksna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a funnel

weeek_create_a_funnel

Create a CRM funnel by specifying name, currency, and privacy. Use this tool to add a new funnel to your sales pipeline.

Instructions

POST /crm/funnels. Create a funnel. Tags: Funnels. Body: application/json.

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

Input Schema

NameRequiredDescriptionDefault
bodyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are present, and the description only gives the HTTP method and endpoint. It does not disclose side effects, permissions, idempotency, or expected outcomes beyond creating a funnel.

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 description is very short (three fragments), but it is not front-loaded with the most critical information. It wastes characters on the endpoint path and tags, which are less important than usage guidelines.

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

Completeness1/5

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

Given the tool has a nested parameter object and no output schema, the description fails to explain the purpose of each field, the expected response, or how a funnel fits into the CRM. It is severely incomplete.

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

Parameters1/5

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

Schema description coverage is 0%, and the description only mentions 'Body: application/json'. No explanation of what 'name', 'isPrivate', or 'currencyId' mean or how they affect the funnel.

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 states 'Create a funnel', which is clear but nearly identical to the tool title. It fails to differentiate from sibling tools like 'weeek_create_a_funnel_status' as it does not clarify what a funnel is or how it differs from other entities.

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?

No guidance on when to use this tool versus alternatives (e.g., updating or deleting a funnel). No prerequisites or context for usage are provided.

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