SyncroMSP MCP Server

payments_get_profile

Retrieve a specific payment profile by customer ID and profile ID to access payment details for billing and customer management.

Instructions

Get a payment profile by ID

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": {
      "customer_id": "<customer_id>",
      "id": "<id>"
    },
    "name": "payments_get_profile"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Payment profile ID
`customer_id`	Yes	Customer ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It only states 'Get a payment profile by ID', which implies a read-only operation, but does not confirm safety, required permissions, or any side effects. This is insufficient for an agent to understand the tool's impact.

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 a single, clear sentence with no redundant words. It is concise and front-loaded, but could include a brief note about required IDs without sacrificing brevity.

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 tool's simplicity and 100% schema coverage, the description lacks information about the return value (since no output schema exists). An agent would benefit from knowing what data the profile contains or that it returns a single object. The description is too sparse for a complete understanding.

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

Parameters3/5

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

The input schema provides descriptions for both parameters (100% coverage), so the baseline is 3. The description does not add any extra meaning beyond what the schema already states, such as clarifying the relationship between customer_id and id or any constraints.

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 clearly states the tool retrieves a payment profile by ID, using a specific verb and resource. However, it does not explicitly distinguish from siblings like payments_list_profiles or payments_get, though the resource name 'profile' and 'by ID' hints at the distinction. A clearer differentiator would be helpful.

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 guidelines are provided on when to use this tool versus alternatives such as payments_list_profiles or payments_create_profile. The description does not include conditions, prerequisites, or exclusions, leaving the agent without context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server