Skip to main content
Glama

Cms Open Payments

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Discloses scoping by identifier, persistence duration (persistent for auth, 24h for anonymous), and is idempotent. Adds significant detail beyond annotations, which already indicate idempotency and non-destructiveness.

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

Conciseness4/5

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

Three focused sentences, front-loaded with purpose. The second sentence is somewhat lengthy but packs useful examples. No fluff.

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

Completeness5/5

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

Complete for a simple two-parameter tool: explains purpose, usage, storage details, and lifecycle with complementary tools. No output schema needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions already cover both parameters (100% coverage). Description adds real-world examples for key (e.g., 'subject_property') and clarifies value as 'any text', enhancing understanding.

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 saves data for later reuse across conversations or sessions, with concrete examples like tickers, addresses, and preferences. It distinguishes itself from sibling tools recall and forget by being the write operation.

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?

Explicitly says when to use ('discover something worth carrying forward') and pairs with recall/forget for full lifecycle. However, it does not explicitly state when not to use it, though the guidance is strong enough.

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

All Cms Open Payments toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Tools like ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are very similar, causing potential confusion. The open_payments_* tools are clearly differentiated, but the mix of generic Pipeworx tools with domain-specific ones creates overlapping purposes.

Naming Consistency2/5

Tool names mix conventions: some use snake_case (ask_pipeworx, open_payments_company), while others use less consistent patterns (deep_research, generate_llms_txt). The open_payments_* tools have a consistent prefix, but the overall set lacks a unified naming scheme.

Tool Count2/5

With 41 tools, the server is heavily overloaded for a domain focused on CMS Open Payments. The majority of tools are general-purpose Pipeworx tools unrelated to the server's name, making the count feel excessive and unfocused.

Completeness3/5

The open_payments_* tools cover the CMS Open Payments domain well (search, company, physician, history, etc.). However, the inclusion of many unrelated Pipeworx tools means the server as a whole is not cohesive, and the completeness of the named domain is overshadowed.

Resources