Skip to main content
Glama
Sign In
boostu-teamleader-mcp

boostu-teamleader-mcp

by boostuagency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

teamleader_deal_sources_list

Retrieve paginated deal sources from Teamleader Focus. Use page and page size parameters to control which sources are returned.

Instructions

List deal sources.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
page_sizeNomax 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior, but it only states the action. It does not mention pagination, read-only nature, rate limits, or response format, leaving the agent without critical context.

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 concise (one sentence), but it is under-specified rather than efficiently packed with value. It reads as a tautology of the tool name, offering no additional insight, so it fails to earn high marks for structure.

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?

Given the minimal schema (no output schema, only two params) and no annotations, the description should explain what a 'deal source' is, how pagination works, and what the response contains. It does none of this, leaving the agent under-informed.

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?

The description does not explain any parameters. While the schema provides a 'max 100' hint for page_size, 'page' remains undefined, and the description adds no meaning about pagination semantics beyond the schema.

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

Purpose4/5

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

The description 'List deal sources' uses a clear verb and resource, making its purpose understandable. It doesn't distinguish itself from sibling list tools by mentioning scope or filtering, but the resource name 'deal sources' is unique enough that the intent is clear.

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 is provided on when to use this tool versus alternatives, or what scenarios it fits. There is no mention of permissions, prerequisites, or exclusions, so the agent receives no decision-making support.

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