Skip to main content
Glama

Enzo's

Homes with video tours

video_tours
Read-only

List for-sale homes that have a real agent-filmed video walkthrough (TikTok), each with its video link. Optionally filter to a metro or state.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-25, default 10).
metroNoOptional metro, city or two-letter state, e.g. 'Los Angeles' or 'TX'.

Output Schema

NameRequiredDescriptionDefault
countNo
homesNo
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds meaningful context beyond that: results are guaranteed to include an actual video link, and the tours are agent-filmed/TikTok-sourced rather than generic media. It does not mention pagination or that results cap at 25 overall.

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?

Two tight sentences, the defining scope is front-loaded, and the optional filtering note follows. Nothing is redundant or 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?

With an output schema present, return values need not be explained, and the description correctly avoids them. For a simple two-optional-parameter read tool the coverage is nearly complete; only minor operational details such as whether results are paginated past the 25 cap are absent.

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%, so both parameters are already documented in the schema, including the 1-25 limit range and the metro/city/state acceptances. The description's restatement of the metro-or-state filter adds no syntax or format detail beyond that, so the baseline of 3 applies.

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 gives a specific verb and resource ("List for-sale homes") plus the defining qualifying criterion: only homes with a real agent-filmed video walkthrough, each including its video link. That criterion is what separates it in practice from search_homes, though no sibling is named 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?

"Optionally filter to a metro or state" is guidance about parameters, not about when to pick this tool over search_homes or below_market_deals. The use case (wanting video walkthroughs) is implied clearly enough to infer, but there are no exclusions or named alternatives.

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