Skip to main content
Glama
Sign In
BlindPay MCP Server

BlindPay MCP Server

by blindpaylabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Put Instances Members By User Id

PutV1InstancesMembersByUserId
Idempotent

Update a BlindPay instance member's role by specifying the instance and user ID, with an optional idempotency key to safely retry requests.

Instructions

Update Instance Member Role

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": {
      "id": "<id>",
      "user_id": "<user_id>",
      "requestBody": "<requestBody>"
    },
    "name": "PutV1InstancesMembersByUserId"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
user_idYes
requestBodyYes
Idempotency-KeyNoOptional key to safely retry this request without performing the action twice. Retrying with the same key and an identical body replays the original response; reusing a key with a different body returns an error. Keys are kept for 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.3

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the name: it does not say whether the role is replaced wholesale, what permissions are needed to change a role, or what errors occur for invalid upgrades.

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

Conciseness3/5

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

A four-word fragment is front-loaded and waste-free, but here terseness is under-specification rather than efficiency; nothing in it earns extra credit beyond the title.

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 mutation with a nested request body carrying a role enum, 3 required parameters, and no output schema, yet the description never explains the role replacement semantics or permission requirements. For a write endpoint that changes access levels, this is materially incomplete.

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 only 25% — only the Idempotency-Key field is documented. The description does not clarify that 'id' is the instance, 'user_id' identifies the target member, or that 'user_role' is the replacement role, so the three required parameters remain ambiguous.

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 pairs a specific verb (update) with a specific resource (instance member role), so an agent knows this mutates an existing member's role rather than creating or deleting one. It does not, however, distinguish itself from siblings such as GetV1InstancesMembers or DeleteV1InstancesMembersByUserId beyond the verb.

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 guidance on when to use this versus GetV1InstancesMembers (to inspect current roles) or DeleteV1InstancesMembersByUserId (to remove a member). No prerequisites, permissions, or call-order conditions are stated.

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