Skip to main content
Glama
Sign In
SyncroMSP MCP Server

SyncroMSP MCP Server

by advenimus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

customers_latest

Retrieve the most recently created customers from SyncroMSP. Use this to view new client records and keep your data current.

Instructions

Get the most recently created customers

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only states it retrieves recent customers, but lacks details on pagination, limit, ordering, or whether it returns all recent customers or a subset. This leaves important behavior ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at one sentence, clearly conveying the core purpose without redundancy. However, it sacrifices necessary detail for brevity, so it is not maximally effective.

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 no output schema and no annotations, the description is insufficiently complete. It does not explain return value format, count of customers, or any constraints, leaving the agent uncertain about how to interpret results.

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?

The input schema has 0 parameters, and the description's coverage is 100%. The description adds meaning by specifying the tool retrieves recent customers, which compensates for the lack of parameters. Following the rule for 0 parameters, baseline 4 is appropriate.

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 'Get the most recently created customers' clearly states the action (Get) and the resource (most recently created customers), distinguishing it from siblings like 'customers_list' and 'customers_get'. However, it does not specify the number of customers returned or the exact criteria for 'most recent', which would enhance clarity.

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. Siblings like 'customers_list' and 'customers_get' exist, but the description does not explain scenarios where 'customers_latest' is preferred, nor does it mention any limitations or prerequisites.

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