Skip to main content
Glama
Sign In

Fless Apartment Hunt

by io.fless
OverviewDiscussionsAdmin

fetch

Read-onlyIdempotent

Fetch full content by id from search: markdown text + canonical url for citations.

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
idYescity:<slug> | neighborhood:<city>:<nb> | doc:hunt-how-to

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 read-only, idempotent, and non-destructive behavior, so the description only needs to add extra context. It usefully specifies the response contains markdown text and a canonical URL for citations, which goes beyond the structured data. It does not cover error behavior, but that is a minor gap given the strong annotation coverage.

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?

The description is a single information-dense sentence. It front-loads the action and resource, then states the output shape, with 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?

For a one-parameter, read-only, idempotent tool, the description adequately covers both input ('by id') and output ('markdown text + canonical url'). Since there is no output schema, the explicit return-value note is valuable. It could be slightly stronger by explicitly saying IDs come from search results, but that is already implied.

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?

The sole parameter id is fully documented in the input schema with concrete format examples (city:<slug>, neighborhood:<city>:<nb>, doc:hunt-how-to). Schema description coverage is 100%, so the description adds no additional parameter meaning beyond 'by id'.

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?

The description states a clear verb ('Fetch'), a specific resource ('full content by id'), and the output ('markdown text + canonical url for citations'). This distinguishes it from sibling search tools, which return lists rather than full content.

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?

The phrase 'from search' implies this is meant for retrieving full content for IDs obtained via search, but it does not explicitly say when to use it versus overlapping siblings like get_city_overview or get_neighborhood. No exclusions or alternatives are named.

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

All Fless Apartment Hunt toolsInspect
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