Skip to main content
Glama
PayStage MCP Server

PayStage MCP Server

evaluate_velocity

Checks a proposed payment against recent action history and velocity policy, flagging rolling-window rate or spend-pattern violations before approval.

Instructions

Rolling-window rate and spend-pattern check for a proposed payment against recent action history and a policy.velocity config

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": {
      "proposed": "<proposed>"
    },
    "name": "evaluate_velocity"
  }
}

Input Schema

NameRequiredDescriptionDefault
now_msNo
policyNo
historyNo
proposedYes
policy_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It indicates a rate/spend check but does not state whether the evaluation is read-only, what it returns (allow/deny result, metrics, or violations), how missing history is treated, or whether the policy config is resolved from an inline object or a path. These omissions are significant for a policy-evaluation tool.

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 definition is a single front-loaded sentence with no filler. However, the compressed phrase 'policy.velocity config' is slightly jargon-heavy and could be clearer without much added length.

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?

This is a complex tool with five parameters, nested objects, no annotations, no output schema, and no schema descriptions. The description does not expose the return contract, required-vs-optional behavior, defaults, or failure modes, leaving substantial gaps an agent would need to resolve before calling it correctly.

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?

Schema description coverage is 0%, and the description names only broad concepts: proposed payment, recent action history, and policy.velocity config. It does not explain the required 'proposed' object's fields, the difference between 'policy' and 'policy_path', the role of 'now_ms', the default empty history, or the amount/amount_atomic/decimals relationship.

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 gives a specific verb-like evaluation ('check') and a precise resource: rolling-window rate and spend-pattern for a proposed payment against history and a velocity policy. It is clearly distinct from generic payment evaluation siblings, though it does not explicitly name the sibling tools it replaces or complements.

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?

There is no explicit guidance on when to use this tool versus the sibling evaluate_* tools, nor any when-not conditions. The phrase 'for a proposed payment' implies a pre-execution context, but the agent must infer that from general knowledge rather than from stated routing guidance.

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