Skip to main content
Glama

Fetch one Flatio listing for deep research

fetch
Read-only

Use this for deep research after search. It takes one id that search returned and gives that listing's facts as text, with the monthly rent and its URL on flatio.com. flatio_get_listing returns the same listing as fields and prices exact dates. Give the guest each listing's url exactly as returned, with all its query parameters.

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

Input Schema

NameRequiredDescriptionDefault
idYesAn id from the results of search, e.g. "95507".

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is known. The description adds genuinely new behavior: output is plain text rather than fields, and the returned URL must be passed to the guest verbatim including all query parameters, which is a real usage constraint not captured anywhere in structured data. It stops short of noting error behavior or size/truncation limits for listing text, keeping it below a 5.

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?

Front-loaded with the usage case, then output shape, then sibling differentiation, then the downstream URL-handling rule — a sensible order with no filler. The final sentence is an instruction about how to relay output rather than about calling the tool, which is slightly off-center but still earns its place by preventing URL mangling.

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, the description needn't enumerate return fields, and it correctly focuses on usage, text-vs-fields distinction, and URL handling. What remains thin is the notion of 'deep research' itself — how much text comes back or whether the result is cached/stable — but for a 1-parameter read tool this is close to complete.

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 coverage is 100% and the single id property already documents its source and gives an example ('95507'). The description restates the provenance constraint ('an id that search returned') without adding format or validation detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: takes one id from search results and returns that single listing's facts as text, including monthly rent and the flatio.com URL. It also explicitly separates itself from flatio_get_listing, which returns the same listing as structured fields with exact date pricing, so an agent can pick the right tool without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening clause 'Use this for deep research after search' supplies the when, and the id provenance ('one id that search returned') pins it to the search flow. The named alternative flatio_get_listing with its distinguishing condition (fields + exact date prices) gives a clear routing rule between the two.

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