Skip to main content
Glama
Sign In

kolmo-mcp-server

by io.kolmo.www
OverviewDiscussionsAdmin

Deposit and invoice payment links

get_payment_link
Read-onlyIdempotent

Invoices for an accepted Kolmo quote, with amount, status and the kolmo.io quote page where the person pays them. Never collect card or bank details.

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": {
      "quoteLink": "<quoteLink>"
    },
    "name": "get_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteLinkYesThe person's kolmo.io/quotes/<id> link, as Kolmo sent it. Never guess one.

Output Schema

NameRequiredDescriptionDefault
messageYes
invoicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / additionalProperties
      Removed value: -true
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety basics are covered. The description adds a critical security rule ('Never collect card or bank details') and clarifies that it operates on accepted quotes, which is valuable context beyond the annotations. It does not disclose return format, but an output schema exists.

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?

Two sentences, front-loaded with the key purpose and followed by a clear safety rule. There is minimal waste, though the first sentence is a fragment ('Invoices for...') rather than a complete clause, which slightly reduces clarity.

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

Completeness4/5

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

Given the simplicity (one parameter), rich annotations, and presence of an output schema, the description provides sufficient context to call the tool correctly. It could explicitly state that it returns a payment link URL and when to use it over get_my_quote, but otherwise it is complete.

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?

Schema description coverage is 100%, and the single parameter quoteLink is fully documented in the schema with a warning not to guess. The description adds no parameter-specific information beyond what the schema already provides, so the baseline 3 is appropriate.

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 states that the tool returns invoices for an accepted Kolmo quote, including amount, status, and the payment page. The verb is implicit (returns/retrieves), but the resource and scope are clear. It distinguishes from get_my_quote by focusing on accepted quotes and payment details, though it doesn't name the sibling explicitly.

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 phrase 'for an accepted Kolmo quote' implies a usage condition, but there is no explicit guidance on when to use this tool versus alternatives like get_my_quote or respond_to_quote. The rule 'Never collect card or bank details' is a behavioral constraint, not usage guidance.

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

All kolmo-mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources