Skip to main content
Glama

Get STR host program info

get_host_program_info
Read-onlyIdempotent

Returns Fold's linen-turnover program for Airbnb / Vrbo / short-term rental hosts: how same-day turnovers work, pricing by host size (à la carte, Fold Club, portfolio volume rates), and how to get started. Use when the user hosts a short-term rental, manages STR properties, or asks about linen/turnover service between guests.

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_host_program_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 is covered. The description adds valuable context about what the returned program information includes: same-day turnover mechanics, pricing tiers, and onboarding.

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?

The description is front-loaded with the core purpose and then gives usage guidance. It is dense but efficient, with no filler sentences, though the long enumeration could be slightly more scannable.

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?

With no parameters, no output schema, and rich annotations, the description gives enough detail for an agent to know when and why to call this tool. It could mention that there are no inputs, but that is already apparent from the empty schema.

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?

There are zero parameters, so the baseline is 4. No parameter semantics are needed, and the description appropriately focuses on the information returned.

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 and resource: returns Fold's linen-turnover program information for Airbnb/Vrbo/STR hosts. It clearly describes the scope of information covered, though it does not explicitly distinguish itself from siblings like get_pricing or get_service_info.

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?

Provides clear usage conditions: when the user hosts a short-term rental, manages STR properties, or asks about linen/turnover service between guests. It lacks explicit when-not-to-use guidance or named alternatives, but the context is strong enough for an agent.

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