Skip to main content
Glama
Sign In
Paymenter MCP Server

Paymenter MCP Server

by dongocanh0501
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

paymenter_get_user_overview

Fetch a consolidated overview of a user's active services, open tickets, recent invoices, and credit balance by user ID.

Instructions

Fetch consolidated user overview including active services, open tickets, recent invoices, and credit balance.

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": {
      "user_id": "<user_id>"
    },
    "name": "paymenter_get_user_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesThe unique numeric ID of the user

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, and the description carries the behavioral load. It does disclose the data categories returned, implying a read-only aggregate, but says nothing about permissions, pagination/limits on the embedded lists, or whether incomplete data is possible for a user with no activity.

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?

One sentence, front-loaded with the verb and resource, and the enumeration of contents earns its place by defining what 'overview' means. No filler.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the returned sections, which is exactly the missing information an agent needs. The only remaining gap is the depth/limits of each embedded collection.

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?

A single parameter with 100% schema description coverage, so the schema already documents user_id fully. The description adds no format hints (e.g., that numeric IDs are typical) or error behavior for unknown users, hitting the baseline rather than exceeding it.

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?

States a specific verb ('Fetch') and a specific composite resource ('consolidated user overview'), then enumerates the constituent parts (services, tickets, invoices, credit). This makes it distinguishable from paymenter_get_user, which presumably returns a single user record, though the distinction is inferred rather than stated.

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?

Usage is implied by 'consolidated overview' - an agent can infer this is a good first-look/summary call - but there is no explicit guidance on when to prefer it over paymenter_get_user, paymenter_list_services, or paymenter_list_invoices, which cover overlapping data.

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