Skip to main content
Glama
upvest-mcp-server

upvest-mcp-server

by Shalom2212

upvest_signature_generator

Generate RFC/IETF draft-compliant HTTP Message Signature headers for Upvest API requests and webhook handlers.

Instructions

Generates RFC/IETF draft compliant HTTP Message Signature headers (v15/v6) required for Upvest API requests and webhook handlers.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "upvest_signature_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRequest URL path and query string (e.g. /orders or /users)
key_idNoUpvest Client API Key ID (defaults to sandbox key if omitted)
methodYesHTTP request method
payloadNoJSON stringified request payload body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses the output type (signature headers) and compliance standards (RFC/IETF drafts v15/v6), but omits auth requirements (e.g., whether a secret key is needed beyond key_id), whether the operation has side effects, and error behavior. It is adequate but leaves clear gaps.

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?

A single, front-loaded sentence with no redundant or vague wording. Every phrase earns its place by specifying verb, resource, standards, and context.

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

Completeness3/5

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

For a simple 4-parameter tool with no output schema and no annotations, the description should explain the return format and any prerequisites (e.g., secret key configuration). It only implies the output and omits these details, leaving an adequate but incomplete picture.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds no further meaning to the parameters beyond what the schema already documents (method, path, key_id, payload).

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

Purpose5/5

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

States a specific verb ('Generates') and resource ('HTTP Message Signature headers'), with precise qualifiers ('RFC/IETF draft compliant (v15/v6)') and usage context ('required for Upvest API requests and webhook handlers'). This clearly distinguishes it from the sibling tools, which concern order simulation and anomaly analysis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context: the tool is needed for Upvest API requests and webhook handlers. No explicit when-not or alternative tools are named, but the siblings serve entirely different purposes, so no further routing guidance is necessary.

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