Skip to main content
Glama

free_tier

Whether the free tier is open right now: since when, until when, how many guests it seats at once, the rule, how to claim and a runnable claim example. Public; needs no pass.

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": "free_tier"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: it is public, requires no pass/credential, and returns a runnable claim example alongside the rule. It does not explicitly say the call is side-effect free or read-only, but the informational framing makes that the natural reading.

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?

One sentence, front-loaded with the core question ('whether the free tier is open right now') followed by an enumerated payload, plus a short qualifier on access. The colon-list is dense but every item maps to real returned content, so nothing is padding.

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?

Since there is no output schema, the description must convey the shape of the return value, and it does so by listing the fields an agent will receive, including the claim example. For a zero-argument informational tool this is nearly complete, with only explicit read-only framing missing.

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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The empty object schema and the description's field list are consistent.

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 the resource precisely — the current state of the free tier — and enumerates the facets it reports (open window, seat count, rule, claim instructions). It is a noun-phrase listing rather than a verb-led statement, and it never names the sibling 'claim_free_tier' outright, so the boundary is implied by 'how to claim' rather than declared.

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?

Usage is only implied: an agent can infer this is the check-first step before calling claim_free_tier, and the description adds the useful precondition 'Public; needs no pass'. There is no explicit when-to-use/when-not or named alternative, so the agent must construct the workflow itself.

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.

Resources