Skip to main content
Glama
dragonkhoi

Ramp MCP

by dragonkhoi

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_credit_card_transactionsC

Retrieve information about your Ramp credit card transactions.

get_ramp_statementsB

Retrieve Ramp statements with optional date filtering and pagination.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves credit card transactions, while the other retrieves statements with filtering capabilities. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool based on the need.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern (get_credit_card_transactions and get_ramp_statements), using the same verb 'get' and snake_case formatting. This predictability aids in tool identification and usage.

Tool Count2/5

With only two tools, the server feels under-scoped for a financial management domain like Ramp, which typically involves more operations such as creating transactions, updating details, or managing accounts. The limited set may hinder comprehensive agent workflows.

Completeness2/5

The tool surface is severely incomplete for a Ramp integration, covering only retrieval of transactions and statements. Missing are essential CRUD operations (e.g., create, update, delete), account management, or other financial actions, leading to significant gaps that will cause agent failures in broader tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues