Skip to main content
Glama
dragonkhoi

Ramp MCP

by dragonkhoi
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • 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.

  • Average 3/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior2/5

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

    With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation but provides no information about authentication requirements, rate limits, pagination behavior (despite having 'start' and 'page_size' parameters), error conditions, or what format the returned information takes. This leaves significant behavioral unknowns for a tool with 26 parameters.

    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, clear sentence that efficiently communicates the core purpose without unnecessary words. It's appropriately sized for a tool description and front-loads the essential information about what the tool does.

    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?

    Given the high complexity (26 parameters), no annotations, no output schema, and 0% schema description coverage, the description is woefully incomplete. It doesn't address what information is returned, how to use the extensive filtering parameters, pagination behavior, or any constraints. For such a complex tool, the minimal description leaves too many questions unanswered.

    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?

    With 0% schema description coverage and 26 parameters, the description provides no semantic information about any parameters. It doesn't explain what filtering capabilities exist, what the various ID parameters represent, or how date ranges work. The description fails to compensate for the complete lack of schema documentation.

    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 clearly states the action ('Retrieve information') and resource ('Ramp credit card transactions'), making the purpose immediately understandable. It distinguishes from the sibling 'get_ramp_statements' by specifying transactions rather than statements. However, it doesn't specify the scope or format of the retrieved information, keeping it from a perfect score.

    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?

    The description provides no guidance on when to use this tool versus alternatives, nor any context about prerequisites or constraints. With 26 optional parameters and a sibling tool for statements, the lack of usage guidance leaves the agent to guess when this specific transaction retrieval tool is appropriate.

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

  • 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 of behavioral disclosure. It mentions 'optional date filtering and pagination', which hints at querying behavior, but it doesn't cover critical aspects like rate limits, authentication needs, error handling, or what the return format looks like (e.g., list of statements, total count). This leaves significant gaps for a tool with no annotation support.

    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 that front-loads the core purpose and key features without any wasted words. It's appropriately sized for the tool's complexity, making it easy to parse quickly.

    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?

    Given the tool's moderate complexity (4 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and hints at functionality, but lacks details on behavioral traits, output format, and differentiation from siblings. This makes it minimally viable but with clear gaps that could hinder effective tool selection and invocation.

    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 description coverage is 100%, with all parameters well-documented in the input schema (e.g., date formats, pagination details). The description adds value by summarizing the optional features ('date filtering and pagination'), but it doesn't provide additional semantic context beyond what the schema already specifies, such as default behaviors or constraints not in the schema.

    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 clearly states the verb 'Retrieve' and resource 'Ramp statements', making the purpose specific and understandable. However, it doesn't explicitly differentiate from the sibling tool 'get_credit_card_transactions', which might retrieve similar financial data but for different resources, leaving some ambiguity about when to choose one over the other.

    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?

    The description mentions 'optional date filtering and pagination', which implies some usage context, but it doesn't provide explicit guidance on when to use this tool versus the sibling 'get_credit_card_transactions' or any alternatives. No exclusions or specific scenarios are outlined, leaving the agent with minimal direction.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

ramp-mcp MCP server

Copy to your README.md:

Score Badge

ramp-mcp MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dragonkhoi/ramp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server