Skip to main content
Glama
Sign In
mcp-venmo

mcp-venmo

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

venmo_add_friend

Send a friend request to any Venmo user by entering their username. Establish connections instantly for payments and social interactions.

Instructions

Send a friend request to a Venmo user.

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": {
      "username": "<username>"
    },
    "name": "venmo_add_friend"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesVenmo username to add as a friend (without @)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It identifies the action as sending a friend request but provides no information about authentication requirements, error states, idempotency, or whether the friend request is immediate or requires approval. This is a significant gap for a mutation tool.

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?

The description is a single, efficient sentence with no filler or redundant information. Every word contributes to understanding the tool's purpose.

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?

The tool is a mutation with no output schema and no annotations. While the single parameter is well-documented, the description omits critical behavioral context such as authentication, possible failure modes, and whether the action is reversible. The minimalism leaves the agent under-informed for a state-changing operation.

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 schema covers the only parameter with a clear description ('Venmo username to add as a friend (without @)'), so schema coverage is 100%. The tool description itself adds no parameter information, but the schema fully compensates, yielding the baseline of 3.

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?

The description clearly states the tool's action: 'Send a friend request to a Venmo user.' This is a specific verb+resource combo that distinguishes it from sibling tools like accept_request/decline_request (which handle incoming requests) and get_friends (which lists existing friends).

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?

The description implies the use case (initiating a friend request) through its wording, but it does not explicitly state when to prefer this over alternatives, nor does it mention prerequisites like being logged in or the target user existing. Usage is inferred rather than directed.

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