affterms — affiliate program terms

Check a featured booking

featured_check_booking

Read-onlyIdempotent

Check a featured booking by the id given after payment (FT- followed by 6 letters and digits): whether it is scheduled, active, expired or removed, its category, and when it starts and ends.

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": {
      "id": "<id>"
    },
    "name": "featured_check_booking"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The booking id, e.g. FT-7K2Q9X.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare read-only, idempotent, non-destructive behavior, but the description adds valuable context by specifying the possible status outcomes (scheduled, active, expired, removed) and the returned fields (category, start/end). It does not cover error handling or rate limits, but with annotations covering safety, this is sufficient for a 4.

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 purpose and efficiently packs the id format and return values. No wasted words.

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 lack of an output schema, the description appropriately enumerates what the check returns (status, category, start/end), making it complete for an agent to understand the outcome. It could mention error cases for invalid ids, but for a simple read-only check it is largely complete.

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 coverage is 100%, so the schema already documents the single id parameter. The description adds format specificity ('FT- followed by 6 letters and digits') and notes the id is 'given after payment', which supplements the schema's example without contradicting it.

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 ('check') and resource ('featured booking'), and enumerates what it returns (status, category, start/end). However, it does not differentiate from sibling tools like featured_availability, leaving the agent to infer when this is the right check.

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?

Provides context that the id is obtained after payment, implying usage post-payment, but offers no explicit comparison to alternatives (e.g., featured_availability) or when not to use it. The when-to-use is implied rather than stated.

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

All affterms — affiliate program terms tools Inspect

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

Need Help?