Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

Plans and quotas

get_plans
Read-onlyIdempotent

List the UFCalendar Fight API plans, their monthly request quotas and per-minute limits, including the free plan (100 requests a month, no card). Answers "what does this cost" without a credential.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and a closed world, so the safety profile is covered. The description adds genuinely new behavioral context: the endpoint is reachable without authentication, and it includes the free tier, which the annotations do not convey.

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?

A single sentence that front-loads the verb and resource, then packs quotas, limits, and the free-plan detail into one compact clause. Nothing is wasted and nothing important is buried.

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?

For a zero-parameter, read-only listing tool with no output schema, the description effectively previews the return shape (plan name, monthly quota, per-minute limit) and adds the auth-free and free-tier facts. There is no meaningful gap left for an agent deciding whether to call it.

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?

The tool takes zero parameters, so there is nothing for the description to clarify; the baseline for a parameterless tool applies. The description correctly implies a fixed, unfiltered response rather than a queryable one.

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?

States a specific verb ('List') and resource ('UFCalendar Fight API plans') and enumerates the contents: monthly request quotas, per-minute limits, and the free plan. It is unambiguous on its own, though it does not explicitly distinguish itself from the adjacent get_usage sibling.

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?

Gives an explicit use case — answering 'what does this cost' — and notes that it requires no credential, which is a real selection signal. It stops short of stating when not to use it or pointing to get_usage for consumption data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.